Hi Daniel,
Lightstreamer uses several Web protocols: WebSockets, Comet, HTTP streaming, etc. to provide a channel over which data can be exchanged in real-time with a client.
It first tries to use WebSockets; if it's not able to establish a WebSocket connection, for instance if the client or browser doesn't support websockets, it tries HTTP Streaming.
If also HTTP Streaming doesn't work, due for instance to some anti-viruses mounted on proxy server, it falls back to HTTP Polling (you may find more details looking at ' Lightstreamer Slides: From Push Technology to the Real-Time Web' [
http://www.slideshare.net/alinone/from-push-technology-to-the-realtime-web ]).
So the first think to do is to understand in which way the server is connecting to the client. But in order to better understand your issue, we need more details: first of all which client version you are using, your deploy environment, if there are any proxies or load balancers in between the server and the clients.
A log file from the server, with possibly only one client connected, will provide a more deep inside view of how connections are handled.
If, also with an improved connection, the client still has problems dealing with a hight rate of messages, then you may act on the maximum frequency for a given subscription, to reduce the number of updates sent by the serve to a client. But first let see how the server connects to the client.
regards
Marco
