Re: What is the perfect application model?
- From: "Radek Cerny" <rcerny@xxxxxxxxxxxxxxx>
- Date: Mon, 5 Nov 2007 11:55:47 +1100
How about a totally abstract model where all the business objects (Fields +
Methods etc) live server-side inside an application server, and the UI is
simply a view into the server objects? Use stateless web service calls to
publish deltas; all business rules etc are server-side. This allows for a
true rich/thin client such as XAML or Flash.
For example, you may have a Person business object with date of birth
(editable) and a readonly Age field. Server-side code watches for changes
in DOB and recalculates Age, and publishes all changes which the cleint
simply renders as its told. To the end user, as soon as he tabs out of DOB,
age changes, although a round-trip to the occurred.
So the client simply understands a fixed schema from the server and has
placeholders for Fields, result sets etc published by the business objects
on the server.
The application server shoul be stateful of course, and simply issue session
handles to clients as they log in.
Traffic is minimal - only Deltas, and you are forced to code properly - eg
abstractly - total separation of the UI from business rules, persistence
etc.
User Interface can be anything - HTML/Javascript (AJAX), Windows Forms,
Flash and most recently XAML.
Thats how we build our RIAs - Rich Internet Applications.
Cheers,
Radek
"Andreas Zita" <info@xxxxxxxx> wrote in message
news:2CF86D5A-7E08-4531-BEE5-3506BFF9694D@xxxxxxxxxxxxxxxx
What is the perfect application model?
Lets say we could run a .NET-applikation on the server in a user-session
and only tunnel the interface to the client, similar to how VNC or Remote
Desktop is working (to any klient setup/os). Wouldnt that be a good thing?
I mean, I find it a little problematic to run an XBAP locally for a number
of reasons. First the client obviously has to run the .NET 3.5 framework
but we also get a bit dissconntected to the datasource. We cant well
download the whole dataset to the client and accessing it through a Web
Service is still not good enough since we wont have persistent objects
that way (?). It would be so much nicer to have one single environment to
run all instances in and only displace/tunnel the interface to the client.
This is how ASP + JavaScript allready works in some way I think but I dont
like neither ASP or JavaScript very much. Its a bit straggling and
cumbersome to work with I think.
What are your thoughts about this? Or am I just talking through my hat
....
/Andreas
.
- Prev by Date: Re: How to debug Powershell commandlets?
- Next by Date: Re: ManualResetEvent / WaitOne
- Previous by thread: Re: What is the perfect application model?
- Next by thread: Dotnet application deployment
- Index(es):
Relevant Pages
|
