-
April 20th, 2007, 05:49 PM
#3
Thank you for the explanation Alex. I was not necessarily looking to circumvent any such restriction, just have control over the text and placement of the error message - in general we consider a popup alert refering to "Lightstreamer" (which the end user may or may not have any knowledge of) is less than friendly. Feeding the error through the normal reporting callbacks already in existence seems preferable - and you can still refuse to start the engine as now.
I will go investigate the alternate engine creation strategies you pointed out, I'd only just my code converted to the loadEngineMinimal method, now I notice it is deprecated!
It is not clear to me what all the consequences of supporting sharing an engine across windows are, especially if the original push page that loaded it is closed. It makes sense for frame based apps, but if multiple browser tabs or windows are open - I'm just not sure.
Similar Threads
-
By jonasby1 in forum Client SDKs
Replies: 3
Last Post: July 27th, 2011, 09:58 AM
-
By sachinpatel2 in forum Client SDKs
Replies: 1
Last Post: March 25th, 2010, 09:04 AM
-
By RichP1 in forum Client SDKs
Replies: 5
Last Post: February 24th, 2009, 10:42 AM
-
By indrajit in forum General
Replies: 2
Last Post: March 5th, 2008, 06:29 AM
-
By jsharpe in forum Client SDKs
Replies: 1
Last Post: April 19th, 2007, 09:24 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 08:03 AM.
Bookmarks