Search:

Kal,

What I mentioned was indeed the nofifyUser() implementation. That's the only possible way to validate a sessionId.

For a more detailed explanation, I will cut&paste, below, a description...

Lightstreamer's authentication scheme is based on an application-level session-id and does not support the HTTP Basic Authentication Scheme (that in any case can be provided by the Web server).

So...

The protocol used to connect to Lightstreamer Server is always the same used to download the Master Push-Page. So if the Master Push-Page is downloaded through HTTP, then HTTP will be used for all...

https://site1.system.com for the web server and https://site2.system.com would be perfect. The domain will be of course "system.com".

Regarding the second part of the question, you cannot use different domain names for Lightstreamer Server and the Web Server, for security reasons. So you cannot use a deployment scenario such as:...