-
February 3rd, 2010, 11:08 AM
#5
Originally Posted by
DarioCrivelli
Because of this browser-dependent behavior, the recommended way of testing when Lightstreamer Server and the Web Server are on the same host and no suitable hostname is available is to assign fake hostnames of the correct format directly on the client machine, by playing on the "hosts" file.
Another consequence is that you can't use hostnames like mycompany.com for the Web Server and push.mycompany.com for Lightstreamer Server, because using mycompany.com as the common superdomain is not supported by all browsers. Hence, this case is officially not supported by the Web client APIs.
Thanks for making this clearer, however I'm still unclear on a few things:
1)what do you mean about the superdomain not supported by all browsers? Earlier you say this is the way to do it in production then you end by saying it isn't the way to do it.
2)In your second post you refer to the Lightstreamer API. Are you referring to the javascript API? Please can you be clear about this as it is very confusing.
3)should I be checking the browser name and setting pushPage.context.setDomain(null) for IE and pushPage.context.setDomain(domain) in firefox?
thanks in advance
Similar Threads
-
By DarioCrivelli in forum Client SDKs
Replies: 0
Last Post: February 17th, 2010, 05:10 PM
-
By riwang in forum Client SDKs
Replies: 1
Last Post: January 7th, 2009, 10:56 AM
-
By achimabeling in forum General
Replies: 1
Last Post: August 20th, 2007, 03:08 PM
-
By Mone in forum Client SDKs
Replies: 1
Last Post: March 28th, 2007, 09:35 AM
-
By Mone in forum Client SDKs
Replies: 0
Last Post: November 9th, 2006, 04:12 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 10:37 AM.
Bookmarks