architecture problem

[djlinsen]

hi

I've build a webservice and a client application, the client
application get's it's information from the webservice, just like it
supposed to. Now comes te problem, the webservice should have an extra
task, and that is maintaining socket connections with a device and send
commands from the client through the webservice to the device. But
because a webservice is session depended the socket is closed when
there is no client application connected to the webservice and the
socket will be created multiple times when multiple client applications
access the webservice. So there should be 1 system.net.socket running
that maintaince connections with multiple devices (asynch socket) and
just the normal webservice that can send commands to a device.

1 solution is to build a seperate socket server application but the
problem is that i don't want that applicatio to poll for commands from
the client application or from the webservice.

Hope someone can help me

Greetz

[Michael Nemtsev]

Hello dj******@gmail.com,

Why not to have the socket server and WebServer acting like Broker -one who
gets socket connection request from client and awake the socketServer, informing
the latest about client and asking him to be ready to get connected?

hi

I've build a webservice and a client application, the client
application get's it's information from the webservice, just like it
supposed to. Now comes te problem, the webservice should have an extra
task, and that is maintaining socket connections with a device and
send commands from the client through the webservice to the device.
But because a webservice is session depended the socket is closed when
there is no client application connected to the webservice and the
socket will be created multiple times when multiple client
applications access the webservice. So there should be 1
system.net.socket running that maintaince connections with multiple
devices (asynch socket) and just the normal webservice that can send
commands to a device.

1 solution is to build a seperate socket server application but the
problem is that i don't want that applicatio to poll for commands from
the client application or from the webservice.

Hope someone can help me

Greetz

---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

[Kevin Spencer]

Check out the System.Runtime.Remoting namespace:

http://msdn2.microsoft.com/en-us/lib....remoting.aspx

--
HTH,

Kevin Spencer
Microsoft MVP
Chicken Salad Shooter
http://unclechutney.blogspot.com

A man, a plan, a canal, a palindrome that has.. oh, never mind.

<dj******@gmail.comwrote in message
news:11*********************@i3g2000cwc.googlegrou ps.com...

hi

I've build a webservice and a client application, the client
application get's it's information from the webservice, just like it
supposed to. Now comes te problem, the webservice should have an extra
task, and that is maintaining socket connections with a device and send
commands from the client through the webservice to the device. But
because a webservice is session depended the socket is closed when
there is no client application connected to the webservice and the
socket will be created multiple times when multiple client applications
access the webservice. So there should be 1 system.net.socket running
that maintaince connections with multiple devices (asynch socket) and
just the normal webservice that can send commands to a device.

1 solution is to build a seperate socket server application but the
problem is that i don't want that applicatio to poll for commands from
the client application or from the webservice.

Hope someone can help me

Greetz