I am testing my application with Internet Explorer 9 and I find that it constantly disconnects. Is this expected? The cycle of status updates looks like this:
CONNECTING
CONNECTED:STREAM-SENSING
CONNECTED:HTTP-STREAMING
CONNECTED:HTTP-POLLING
DISCONNECTED:WILL-RETRY
CONNECTING
CONNECTED:STREAM-SENSING
CONNECTED:HTTP-STREAMING
CONNECTED:HTTP-POLLING
DISCONNECTED:WILL-RETRY
CONNECTING
CONNECTED:STREAM-SENSING
CONNECTED:HTTP-STREAMING
CONNECTED:HTTP-POLLING
DISCONNECTED:WILL-RETRY
When I subscribe I use getItems to transform the item to include the session id. I then make use of the session passed to my sendMessage() method to retrieve the handler object and return the smartUpdate. However, since it is constantly disconnecting and reconnecting (and therefore getting a new session each time) more often than not my request/response cycle is broken.
The cycle is quite long running (500-600ms) so by the time my adapter is ready for the smartUpdate the session that originated the request has gone.
This cycle of connect/disconnect is evident with the Lightstreamer demos also.
The only thing that does not exhibit this behaviour (that I have) is the "Hello World" example. With this there is a constant process of updates going on between the server and client, and in this instance the client does not keep disconnecting.