-
November 8th, 2007, 10:31 AM
#1
Richard,
You should not do that. Lightstreamer should directly handle the connections with the clients in order to optimized the bandwidth (adaptive streaming) and to absorb the load on itself without impacting on Tomcat. But shoud you need to do that, you should probably use a reverse proxy to route the requests to Tomcat or Lightstreamer. Or perhaps code a servlet that does the right routing.
In any case, this is not a common practice with Lightstreamer.
Cheers,
Alessandro
-
November 9th, 2007, 05:26 PM
#2
Thanks Alessandro,
Do you think using Apache as a proxy for both Lightstreamer and Tomcat would be a reasonable solution? The client in this case will be hosting the system and they only have a single machine available, so this might have to be the way forward for now.
Cheers,
Richard
-
November 10th, 2007, 06:15 PM
#3
Richard,
That could work, if you can route the requests based on the URL path (for example requests beginning with "/lightstreamer" should go to Lightstreamer Server). Of course, if you need thousands of concurrent push sessions, Apache would become the bottleneck.
Another solution would be to have two network cards or to use some virtualization software in order to have two different IPs listening on port 80.
Similar Threads
-
By bhathiya in forum Client SDKs
Replies: 2
Last Post: April 11th, 2011, 08:38 AM
-
By yzhengyu in forum General
Replies: 1
Last Post: January 20th, 2011, 11:22 AM
-
By Pradeep Chahal in forum General
Replies: 1
Last Post: February 4th, 2010, 05:31 PM
-
By sarbao in forum Client SDKs
Replies: 2
Last Post: April 20th, 2009, 01:02 PM
-
By sarbao in forum Adapter SDKs
Replies: 1
Last Post: April 20th, 2009, 09:29 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:51 PM.
Bookmarks