<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: JSJaC v1.3.2 released</title>
	<atom:link href="http://blog.jwchat.org/2008/12/09/jsjac-v132-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jwchat.org/2008/12/09/jsjac-v132-released/</link>
	<description>coding and stuff</description>
	<pubDate>Fri, 30 Jul 2010 01:45:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Steve</title>
		<link>http://blog.jwchat.org/2008/12/09/jsjac-v132-released/#comment-224390</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 04 Jan 2010 08:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwchat.org/?p=111#comment-224390</guid>
		<description>alex, you shouldn't use apache and mod_proxy withh 2k+ concurrent users. apache is not designed to handle such scenarios as http binding uses long term polling techniques and this results in many concurrent connections which will probably overload your apache. 
you'd be better of to put something like nginx, lighttpd or so in front of apache redirecting every call to /http-bind/ directly to your openfire's BOSH service and anything else back to your apache.</description>
		<content:encoded><![CDATA[<p>alex, you shouldn&#8217;t use apache and mod_proxy withh 2k+ concurrent users. apache is not designed to handle such scenarios as http binding uses long term polling techniques and this results in many concurrent connections which will probably overload your apache.<br />
you&#8217;d be better of to put something like nginx, lighttpd or so in front of apache redirecting every call to /http-bind/ directly to your openfire&#8217;s BOSH service and anything else back to your apache.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex hu</title>
		<link>http://blog.jwchat.org/2008/12/09/jsjac-v132-released/#comment-224384</link>
		<dc:creator>alex hu</dc:creator>
		<pubDate>Sun, 03 Jan 2010 05:29:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwchat.org/?p=111#comment-224384</guid>
		<description>Sir, I need your help!

I integrated jwchat into our web application. when the user log in, he/she will be connected to our openfire server automatically through jwchat(I customized it). here is the issue: after the users get connected, I saw bunch of http-bind POST calls every 2-3 seconds from user browsers to our apache server(there is web proxy configured in the apache server to forward requests to our openfire server). Now after we deploy to production. our server crashed. they think this frequent http-bind calls flooded in to apache server and killed our server.

I searched the Internet, never see any discussion regarding whether or not this http-bind POST calls will kill the servers. is there any steps I possibly doing wrong?

we have at most 2000 concurrent users, is there anyway we can solve it, either by changing our implementation or configuration or upgrade our server hardware architecture.</description>
		<content:encoded><![CDATA[<p>Sir, I need your help!</p>
<p>I integrated jwchat into our web application. when the user log in, he/she will be connected to our openfire server automatically through jwchat(I customized it). here is the issue: after the users get connected, I saw bunch of http-bind POST calls every 2-3 seconds from user browsers to our apache server(there is web proxy configured in the apache server to forward requests to our openfire server). Now after we deploy to production. our server crashed. they think this frequent http-bind calls flooded in to apache server and killed our server.</p>
<p>I searched the Internet, never see any discussion regarding whether or not this http-bind POST calls will kill the servers. is there any steps I possibly doing wrong?</p>
<p>we have at most 2000 concurrent users, is there anyway we can solve it, either by changing our implementation or configuration or upgrade our server hardware architecture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.jwchat.org/2008/12/09/jsjac-v132-released/#comment-223464</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 16 Dec 2008 18:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwchat.org/?p=111#comment-223464</guid>
		<description>Maty, it's really just minor bug fixed plus what was needed to make jsjac work with firefox 3. If you need to get the full picture have a look at

http://trac.jwchat.org/jsjac/changeset?old_path=%2Ftags%2Fjsjac-1.3.1&#038;old=472&#038;new_path=%2Ftags%2Fjsjac-1.3.2&#038;new=494</description>
		<content:encoded><![CDATA[<p>Maty, it&#8217;s really just minor bug fixed plus what was needed to make jsjac work with firefox 3. If you need to get the full picture have a look at</p>
<p><a href="http://trac.jwchat.org/jsjac/changeset?old_path=%2Ftags%2Fjsjac-1.3.1&#038;old=472&#038;new_path=%2Ftags%2Fjsjac-1.3.2&#038;new=494" rel="nofollow">http://trac.jwchat.org/jsjac/changeset?old_path=%2Ftags%2Fjsjac-1.3.1&#038;old=472&#038;new_path=%2Ftags%2Fjsjac-1.3.2&#038;new=494</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maty</title>
		<link>http://blog.jwchat.org/2008/12/09/jsjac-v132-released/#comment-223449</link>
		<dc:creator>Maty</dc:creator>
		<pubDate>Tue, 16 Dec 2008 07:15:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwchat.org/?p=111#comment-223449</guid>
		<description>the changelog file in the download zip file has only details on the changes in version 1.3.1. could you please provide some details on the changes between 1.3.1 and 1.3.2 (looking at the trac system, i see only one closed issue for this version)?
Thanks,
Maty.</description>
		<content:encoded><![CDATA[<p>the changelog file in the download zip file has only details on the changes in version 1.3.1. could you please provide some details on the changes between 1.3.1 and 1.3.2 (looking at the trac system, i see only one closed issue for this version)?<br />
Thanks,<br />
Maty.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
