<?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: XIFF (and SparkWeb) now support BOSH 1.6</title>
	<atom:link href="http://gsoc.safasofuoglu.org/2008/08/04/xiff-and-sparkweb-now-support-bosh-16/feed/" rel="self" type="application/rss+xml" />
	<link>http://gsoc.safasofuoglu.org/2008/08/04/xiff-and-sparkweb-now-support-bosh-16/</link>
	<description>Updating and Improving BOSH Support of Openfire</description>
	<pubDate>Thu, 11 Mar 2010 02:31:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Recent Links Tagged With "ejabberd" - JabberTags</title>
		<link>http://gsoc.safasofuoglu.org/2008/08/04/xiff-and-sparkweb-now-support-bosh-16/#comment-239</link>
		<dc:creator>Recent Links Tagged With "ejabberd" - JabberTags</dc:creator>
		<pubDate>Sun, 26 Oct 2008 01:20:30 +0000</pubDate>
		<guid isPermaLink="false">http://gsoc.safasofuoglu.org/?p=21#comment-239</guid>
		<description>[...] public links &#62;&#62; ejabberd   Safa Sofuoğlu: XIFF (and SparkWeb) now support BOSH 1.6 Saved by hrktir on Fri 24-10-2008   ejabberd doesn’t run after apt-get install ejabberd Saved by [...]</description>
		<content:encoded><![CDATA[<p>[...] public links &gt;&gt; ejabberd   Safa Sofuoğlu: XIFF (and SparkWeb) now support BOSH 1.6 Saved by hrktir on Fri 24-10-2008   ejabberd doesn’t run after apt-get install ejabberd Saved by [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Safa Sofuoğlu</title>
		<link>http://gsoc.safasofuoglu.org/2008/08/04/xiff-and-sparkweb-now-support-bosh-16/#comment-32</link>
		<dc:creator>Safa Sofuoğlu</dc:creator>
		<pubDate>Mon, 18 Aug 2008 20:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://gsoc.safasofuoglu.org/?p=21#comment-32</guid>
		<description>Hi,

&lt;a href="http://www.igniterealtime.org/issues/browse/JM-1412" rel="nofollow"&gt;JM-1412&lt;/a&gt; resolved the issue you mentioned. The server should expect the 'rid' attribute to be within a window of values greater than the 'rid' of the previous request. The size of the window is defined by the 'requests' parameter.

Openfire now handles it this way:

If a request with 'rid' attribute greater than expected arrives, openfire holds it in the queue and waits for another request. When all requests in the sequence have been arrived, openfire processes and responds to them in correct order.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p><a href="http://www.igniterealtime.org/issues/browse/JM-1412" rel="nofollow">JM-1412</a> resolved the issue you mentioned. The server should expect the 'rid' attribute to be within a window of values greater than the 'rid' of the previous request. The size of the window is defined by the 'requests' parameter.</p>
<p>Openfire now handles it this way:</p>
<p>If a request with 'rid' attribute greater than expected arrives, openfire holds it in the queue and waits for another request. When all requests in the sequence have been arrived, openfire processes and responds to them in correct order.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pablo</title>
		<link>http://gsoc.safasofuoglu.org/2008/08/04/xiff-and-sparkweb-now-support-bosh-16/#comment-30</link>
		<dc:creator>pablo</dc:creator>
		<pubDate>Mon, 18 Aug 2008 16:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://gsoc.safasofuoglu.org/?p=21#comment-30</guid>
		<description>Hi,

Is it possible that requests the client make will get to the server in the wrong order? Maybe when the server is busy and the client send requests fast enough?

How do you handle it?
Do you think the client should verify that it is not sending requests too fast or is it the server esponsibility?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Is it possible that requests the client make will get to the server in the wrong order? Maybe when the server is busy and the client send requests fast enough?</p>
<p>How do you handle it?<br />
Do you think the client should verify that it is not sending requests too fast or is it the server esponsibility?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
