Modularity and commonality

Topics: CAB & Smart Client Software Factory
Feb 3, 2006 at 1:13 PM
originally posted by: ksunair

I like the concept used in CAB and I like it. How do we handle common elements in the MVC model? To be precise, when a user login in (it is done through a workitem. This handles wide varity of loggin in), we need to retain the user information through out the session of the application life.

What is a best or CAB approved way of handling this data? This data might be required in different services.

Thanks in advance.
Feb 4, 2006 at 5:25 AM
originally posted by: DLorenz

My guess would be to setup the information thru:

Feb 4, 2006 at 7:33 AM
originally posted by: WalkingDisaster

If it should be avialable to all pieces of your application, the best fit would probably be as a service. In fact, you can probably replace CAB's implementation of IAuthenticationService with your own. Problem is that if you don't want to use the default WindowsPrincipalAuthenticationService.cs, you'll need to use a custom CabApplication implementation to prevent the service from being loaded.
Feb 7, 2006 at 7:09 AM
originally posted by: ksunair

So I can create a service which will perform the validation through a service. Once validated and data is available in the service, this service will be available all through the life of the application?