Results 1 to 2 of 2
  1. #1
    Member
    Join Date
    Apr 2007
    Location
    Kerry
    Posts
    17

    Integration scenario

    Hi guys,

    First of all, Congratulations! The projet seems quite good.

    Now, I'm evaluation this project as an option to be included in a trading application, the impact and consequences, performance, etc. The first point I am looking at is integration with our infrastructure and possible client infrastructure. So I have some doubts that aren't really exclusion facts for lightstreamer but that I'm quite interested to know for seeing how many options we have to sell this to final customers or to negotiate with them.

    So, my first concern, and please correct me if I'm missing the point, is the need of two open ports. This is, one for the lightstreamer server and another one for a normal http server. The first one will serve the streamed content and the second one will server regular html content. Banks are normally reluctant to open ports to the wild west so correct me if I'm wrong.

    Second question related with the first one. Imagine that a bank is so strict that forces you to go through their Apache/IIS systems. Is that possible with your solution? Doesn't that break all the advantages of NIO and socket/thread multiplexors?

    Kind Regards,
    Martin

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan, Italy
    Posts
    515
    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

  1. GWT integration
    By hamroune in forum Client APIs
    Replies: 1
    Last Post: January 3rd, 2012, 09:26 AM
  2. GWT integration
    By hamroune in forum General
    Replies: 1
    Last Post: January 3rd, 2012, 09:26 AM
  3. GWT Integration
    By tvseshagiri in forum Client APIs
    Replies: 1
    Last Post: June 7th, 2010, 11:11 AM
  4. More tables in one page scenario
    By cbrogliato in forum Client APIs
    Replies: 1
    Last Post: October 2nd, 2009, 02:13 PM
  5. Unusual scenario with lightstreemer client
    By mnenchev in forum Client APIs
    Replies: 3
    Last Post: August 28th, 2009, 10:06 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 10:12 AM.