-
June 18th, 2010, 03:26 PM
#7
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 normal operations of Lightstreamer's API.
For the time being, I have worked that around by forcing the usage of BrowserHttp creator for requests created to the Lightstreamer URL, and now the browser process shuts cleanly down when its window is closed.
Thank you,
Emilio
PS
As a side note, I observed that I was not able to establish a streaming connection when using ClientHttp creator. I can now do that using BrowserHttp.
Similar Threads
-
By cara713 in forum Client SDKs
Replies: 1
Last Post: January 13th, 2012, 08:54 AM
-
By kkrisjoy in forum Client SDKs
Replies: 7
Last Post: December 17th, 2010, 09:30 AM
-
By chuan_ckc in forum Client SDKs
Replies: 7
Last Post: December 17th, 2009, 10:15 AM
-
By gjoseph in forum Client SDKs
Replies: 1
Last Post: November 13th, 2009, 11:14 AM
-
By markgoldin in forum Client SDKs
Replies: 5
Last Post: September 26th, 2008, 11:28 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 10:32 AM.
Bookmarks