How can I save (serialize) the clients currently connected to a WCF service?

Question

0.00/5 (No votes)

See more:

Dear All,

my Question goes like this:

How can I save the clients that are currently connected to a WCF service, so that the service can load them after it has been restarted?

My current Scenario is as follows:
I have clients that connect to a Service in a Publish /Subscribe way. The service keeps an internal list that stores the Client Callbacks, so the server can communicate with them at any given time.
The Clients do not change very often. Once a month or so a new Client gets added or one gets removed. They are online every time.

I would now like to be able to serialize the callbacklist with all the clients, so I can load them after the service has been restarted. This way the service could talk to the clients without having them to subscribe again.

Some toughts
- I'd like to avoid any client polling (e.g. firing up a method periodically so a client gets connected again after the service has been restarted)
- I don't want the Clients to be manually configured on the services side.
- Maybe there is some way to read/save the connection credentials from a calling client without using callbacks. Then I could connect in a normal way....

Thanks in advance for your help

Best regards

immes

Posted 1-Feb-13 1:22am

immes

Updated 1-Feb-13 5:48am

v5

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2013-02-01T04:06:00

Solution 1

I have my doubts about this working. What happens if you save the delegate, but the client app closes, possibly because your service isn't responding?? Now you've got a callback to a client that doesn't exist any more. What then??

Posted 1-Feb-13 4:06am

Dave Kreskowiak

immes · Answer 2 · 2013-02-01T05:46:00

Solution 2

Hi,

that is no Problem. When this happens I will delete the client from the list.
He can connect again later.
Regarding the overall process this is fully acceptable.

Posted 1-Feb-13 5:46am

immes