dotnet remoting: 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.OpenRead();
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

almir <kazazic@gmail.com> wrote in news:1192574853.046470.71180
@k35g2000prh.googlegroups.com:

[quoted text, click to view]

I use option #2

http://www.codeproject.com/csharp/RemotingAndEvents.asp

[quoted text, click to view]

Definately not.

[quoted text, click to view]

WCF has 2-way callbacks built in ... might be a better choice.

Or perhaps a 3-party framework like RemObjects?