notifing clients about server events

[almir]

hi,

i need to notify clients about change that happened on server. there
will be about 2000 clients each will have my service running in it,
what would be the best way to notify only few of them them (not all)
about event on server.
i think that using .net events is not an option in this case and I do
not want to pool frorm client or leave open ports on client :)
my idea would be to host a remoting application in IIS (I asume that
it will take better care about so many sockets than written-by-me
simple application could - but maybe I am wrong) open socket to
server
from client, and server would go through all clients in a big array
of
open connections and compare their IP adresses with the ones which
should get notification. if connection is broken, client will simple
reopen it-this is not a problem.
my idea is to use:

WebClient.OpenR ead();
on client and wait for input from server as soon as something comes
to
client huraay-its an event
would it be better to use simple socket classes instead of webClient?
is in this case HttpKeepAlive better or worse option
is there a cleaner solution for this?
thanks
almir

[John Saunders [MVP]]

"almir" <ka*****@gmail. comwrote in message
news:11******** **************@ i38g2000prf.goo glegroups.com.. .

hi,

i need to notify clients about change that happened on server. there
will be about 2000 clients each will have my service running in it,
what would be the best way to notify only few of them them (not all)
about event on server.

I've never done this before, but in the .NET Remoting case, you won't have
to go through a big loop. I believe you can use normal .NET events. All the
clients listening for the event on a particular instance of the remoted
object will be notified when the server raises the event.
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer