Daniel Ockeloen wrote:
I second jms for this, could you also put 'protection by sending cloud id/name' to each message. This is a danger point of the current implementation. Also Andre's problems at the start of the thread are not (imho) related to multicast itself but a until not defined/found problem of why a burst and more important why is this
a problem on the clientside (since they should be really quick).

It is a problem on teh client side because teh client side starts all the threads.
The server side has one thread firing a multitude of commands. The client side changes these commands into an equal number of threads to carry out that command.
This is, I think, what causes the problems.


--
Pierre van Rooden
Mediapark, C 107 tel. +31 (0)35 6772815
"Never summon anything bigger than your head."




Reply via email to