Re: [Jwchat-devel] BOSH Proxy Performance

[Stefan S. <st...@ze...>]

Hi Florian,

you're fully right there. Things you could do to make things scale: Use
apache's mpm-worker model, use a different proxying server like lighttpd
or use some advanced loadbalancer that's capable of doing switching
based on HTTP introspection (like F5's BigIP do). 

Cheers, Steve

Am Sonntag, den 17.02.2008, 12:27 +0100 schrieb Florian Sailer:
> Hey Everyone!
> 
> I have a question which is more concerning jwchat`s underlying jsjac library.
> As i could not find a dedicated list for jsjac,  i hope i can get an answer here... 
> 
> I have learned so far, that due to "The Same Origin Policy", it might be required
> to proxy BOSH requests to the XMPP server. The README coming with jsjac
> suggests to do this using apache`s mod_proxy_http.
> 
> As far as i understand, works BOSH based on long lasting HTTP request. My question 
> is: Does each of such request block the apache instance acting as its proxy? 
> This might not be a problem if you have only a few xmpp connections but 
> as soon as a few hundred users are trying to connect, this would require substantial 
> resources on the system running the apache. 
> 
> Is this assumption right, or am i completely wrong here? If this is correct, what would 
> be a better solution to do the proxy work?
> 
> Thank you very much in advance!
> 
> Florian
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> JWChat-devel mailing list
> JWC...@li...
> https://lists.sourceforge.net/lists/listinfo/jwchat-devel