-
April 7th, 2007, 12:00 PM
#2
Hi Martin,
Thanks.
Lightstreamer Server and the Web Server (e.g. Apache or IIS) are usually deployed on different machines, with different addresses, but on the same ports; for example:
- www.bank-name.com - port 80 (or 443) --> web server
- push.bank-name.com - port 80 (or 443) --> lightstreamer server
This means that the browser just performs very normal connections on very normal ports. Nothing needs to be changed in the firewall configurations on both the client and the server side.
Lightstreamer Server is seen as a normal Web server by the network infrastructure. As you can see in the second architecture diagram on this page (http://www.lightstreamer.com/architecture.htm) the browser should connect directly to both the Web Server and Lightstreamer Server, so that LS Server can have direct control over bandwidth and network congestions, besides offering great connection scalability.
In our experience, this architectural scenario has always been well accepted by banks and financial institutions.
Cheers
Similar Threads
-
By hamroune in forum Client SDKs
Replies: 1
Last Post: January 3rd, 2012, 09:26 AM
-
By hamroune in forum General
Replies: 1
Last Post: January 3rd, 2012, 09:26 AM
-
By tvseshagiri in forum Client SDKs
Replies: 1
Last Post: June 7th, 2010, 11:11 AM
-
By cbrogliato in forum Client SDKs
Replies: 1
Last Post: October 2nd, 2009, 02:13 PM
-
By mnenchev in forum Client SDKs
Replies: 3
Last Post: August 28th, 2009, 10:06 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 06:35 AM.
Bookmarks