After some analysis I found that our application sets as default HTTP request creator the ClientHttp one, instead of the default BrowserHttp. Doing this seems to somehow have side effects on the...
Type: Posts; User: emiliob
After some analysis I found that our application sets as default HTTP request creator the ClientHttp one, instead of the default BrowserHttp. Doing this seems to somehow have side effects on the...
I already tried that here (same configuration Win7+ SL4) both with the online version and a version hosted by my local Lightstreamer server and in those cases the browser did shut gracefully down...
Hi,
Unfortunately the browser seems to stay alive forever. I've tried both with Firefox 3.6.3 and IE 8 (v 8.0.7600.16385) running my client on Silverlight 4, with the same result: the browser...
Hi,
When I try to quit my silverlight client by closing the browser window, the browser process remains hang. It looks like that some internal trheads spawned by the Lightstreamer API are...
Hi Alessandro,
Thanks for the information.
Emilio
Just to add some new info.
I fixed a couple of problems in my code and reconnection after first failure has never failed again since then.
Ciao,
Emilio Bova
Hi,
I did some tests with a Silverlight 4 application, Lightstreamer server 3.6 build 1463, SL API 1.2.0.0.
It appears that the client is able to reconnect to the server even if the very first...
Not yet, but I'll be doing it (hopefully) soon.
I'll post an update as soon as I have news.
Grazie,
Emilio Bova
Hi Mone,
Thanks for your answer... I suspected as much, since I observed that in the faulty case, no requests were sent from the Silverlight API on the net.
However, googling around I found...
Hi,
Since the Silverlight API does not provide the LSProxy class, I'm implementing a mechanism that automatically reconnect my application to the Lightstreamer server in case the connection drops....