WCF Service is only used for communication, it provides data. Application
logic that handles these data has to be separate from the service code
One of the reasons why data handling layer (in your case its persistent
collection) must be separated from service is that
communication layer can change. While logic that handles data usually
remains the same.
With best regards, Vadym Stetsiak.
You wrote on Thu, 11 Oct 2007 02:57:14 -0400:
M> I have the following scenario and problem.
M> What I have I s WCF service hosted inside a Windows Application,
M> which is the server components.
M> I also have a client application, another windows app.
M> The client application calls a service method called
M> AuthenticateUser(), if it succeeds return true, else return false.
M> What I want is the server windows app (the one that host the service
M> on the server side) to some of the action taken by the client apps.
M> For example, every time that a client authenticates, I want the
M> server application to maintain in its main windows a list of all the
M> How can I achieve this?
M> Should all the functionality be in the service, like a collection
M> with the client IDS of the authenticated people?
M> Or it should be on the server app?
M> I'm a bit confused on how to achieve this.
M> Please help.