jhang0315
Hi
For our business needs, we have multiple domain name for our company site. (*.mycompany.com, *.ourcompany.com) Because of the "same origin policy", it seems we need to setup multiple-hosting for our push mechanism. (i.e. push.mycompany.com, push.ourcompany.com, etc.)
Can you please help to verify?
- Is it the best practice to handle this situation?
- what is the maximum number of domain available for multihosting?
- is the setup similar to 2.2.1.1 of clustering.pdf if all our push servers are behind load balancer?
regards
Ken
Dario Crivelli
I cannot exactly understand some details of your question.
Are you referring to Lightstreamer 4 (Duomo) or to the forthcoming 5 (Colosseo)?
Moreover, are you really in a clustering scenario, or did you report Clustering.pdf only as an example?
In fact, the answers may differ in the various cases.
(According to the reported paragraph of Clustering.pdf, you seem to be interested in an answer for Colosseo, which is actually more complex than the Duomo case).
Only the second question has a common answer:
Lightstreamer does not pose constraints on the number of different hostnames that you can use to address a single running instance of the Server.
jhang0315
Thanks for reply,
We have 2 push servers running in clustering mode which makes us quite similar to what clustering.pdf described.
Our servers are in version 3.6. Is there any problem for the multi-hosting for this version?
regards,
Kenneth
Dario Crivelli
As you referred to a paragraph of Clustering.pdf that is only present in Lightstreamer Colosseo but are using quite an old version of Lightstreamer, this may create confusion, as some details are different between the two versions.
That said, yes, your can take inspiration on paragraph 2.2.1.1 of the Colosseo version of the document.
In a multihosting scenario, as we know, the PushPage must address the Server with a URL which is consistent with the URL used by the browser to address the page.
This should be an application job, which should not involve Lightstreamer directly.
However, if you are in a clustering scenario and are leveraging the <control_link_address> and/or <control_link_machine_name> to ensure the "stickyness" behavior, then the URL used by the PushPage to address the Server is determined by that setting.
Hence you have no choice but to set the optional <control_link_machine_name>, which overrides <control_link_address>, to ensure that the Server identifies itself in a way consistent with the one used by the client to address it.
Moreover, if your constraint is that only the Load Balancer should be visible from the internet and if you don't use https, so that the Load Balancer is able to route the requests based on the "host" header, then yes, you can refer to the table in paragraph 2.2.1.1
