-
April 1st, 2008, 10:02 AM
#2
Hello,
first of all there is an error in the seekEngine call. You pass to that method a self pointer but you should pass to it a pointer to the master pushpage's window. By the way the library should be able to reach the master pushpage with the name you give (that's correct)
i.e. If the second pushpage is an iframe inside the master one, than you could call
see seekEngine doc for further details.
returning back to your issue I'm confident that is something you should not worry about.
The "unable to find the engine..." alert is a warning message that appears if after some efforts the page wasn't able to bind to the engine. Usually pages showing that alert after a while succed to find their engine and then them receive their data correctly. This issue is due to downloading times.
Is this your case? If it is, just disable the debug alerts on your production environment and everything will be ok.
see http://www.lightstreamer.com/docs/cl...sOnClientError
let me know if that's not your case (i.e. pages showing the alert never start streaming) or if you want further clarification.
HTH.
Similar Threads
-
By dimitarn in forum Client SDKs
Replies: 6
Last Post: March 26th, 2010, 04:09 PM
-
By jamesclinton in forum Client SDKs
Replies: 29
Last Post: April 30th, 2009, 01:37 AM
-
By ningping in forum Client SDKs
Replies: 1
Last Post: August 6th, 2008, 11:05 AM
-
By eduramires in forum Client SDKs
Replies: 3
Last Post: February 4th, 2008, 09:14 AM
-
By eduramires in forum General
Replies: 1
Last Post: January 29th, 2008, 05:03 PM
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 04:09 PM.
Bookmarks