Hi,
the idea is to rethink your solution and see if you can avoid events. If
you can not, the ok, go with it. In your situation you have 2 options:
1. events - this is easiest and natural way. Just be sure to implement
some kind of your own broadcasting machine, because you can have
problems with native events support if some of the clients fails. Then
all other clients will not receive the event as well. You cant read this
article for ideas:
http://www.genuinechannels.com/Content.aspx?id=27&type=1 2. Create a separate thread at the client and at regular intervals pull
from the server the new state. If you change the state of the server
really often, then this will not create a big overload. But this is
unreasonable if you lets say change server state every 1/2 hour, but
pull for new state every 30 secs.
Sunny
In article <8f1b5e2a.0406290535.cef1bc6@posting.google.com>,
le_khan@yahoo.fr says...
[quoted text, click to view] > Hi NG
>
> In one of his numerous articles, Ingo Rammer advise the .net remoting
> developpers not to use events for networked application.
> I'm a newbie in programming and actually, I do use events in my .net
> remoting application...since I haven't yet found other ways to do what
> I want.
>
> Here is the actual scenario :
> When changes are made on the remote object (Singleton SAO) by a
> client, this client send a notification event to the server
> So that the server will make some computations and notify all the
> clients of the changes by events
> The clients will thus refresh the display
>
> How could I implement this without using events?
>
> thank you
> k