Re: Application objects in UIP -- dotnet distributed apps

Robert Koritnik
10/11/2004 12:44:09 PM

Yes, that's true. Controllers are just class libraries that should be just a
"link" between UI and business objects and as those they cannot directly
(they should not) access Application/Session/Cache objects. They should be
used for Web/Win applications and accessing Application object collection
would interfere with the MVC concept. Actually using Application/Cache usage
already intereferes with this concept, while you cannot directly make
different windows clients to comunicate with eachother.

What I would do is I would extend UIP block code to create another
configurable object for client shared data as Application/Cache can be used.
And put another propery into ControllerBase class called SharedState or
something simmilar.

But you have to know the UIP block very well to do this.

--
RobertK
{ Clever? No just smart. }

[quoted text, click to view]

Deepak Kashyap
10/11/2004 2:57:04 PM

Hello Robert,
But as far as I know, Application and Cache objects are not accessable in
the controller class. I'm managing all the session information in the state
object in the controller class. If we need to manage application level
objects, what is the right approach.

Deepak

Use exactly those... Application and cache. Each for it's own purpose. State
can be anywhere. Normally it uses Session collection, but could also be in
Database, XML file or any other store...

--
RobertK
{ Clever? No just smart. }

[quoted text, click to view]

dotnet distributed apps : Re: Application objects in UIP