"Bill Gower" <billgower@xxxxxx> wrote in message
news:%23vMQ9oJ%23HHA.4736@xxxxxx
>I have a class called LWUser which contains the properties and methods that
>represent a user of the system. This class sits in the Business Services
>solutions on the server. I also have a class called LWUserUI which sits on
>the client side in the Client solution. I am going to create a third
>class, LoggedInUser, a singleton class, which holds information such as
>security access, user info for the current logged in user. I am going to
>use a singleton class as there can only be one user logged in and I need
>this information throughout the app. Where should the class, LoggedInUser
>sit, in the the UI solution on the client side or in the Business Services
>solution on the server side? Where does the concept of "logged-in" sit? Is it an aspect of the LWUser
class or of the LWUserUI class? The LoggedInUser class should sit nearest
where it gets its data from.
On the other hand, if "LoggedInUser" is a unique concept that isn't
dependant on either the businesss services layer or on the UI, then perhaps
it should be its own service.
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer