<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: XMPP Is Better With BOSH</title>
	<atom:link href="http://metajack.wordpress.com/2008/07/02/xmpp-is-better-with-bosh/feed/" rel="self" type="application/rss+xml" />
	<link>http://metajack.wordpress.com/2008/07/02/xmpp-is-better-with-bosh/</link>
	<description>a blog about startups and code</description>
	<lastBuildDate>Thu, 18 Dec 2008 03:41:49 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: metajack</title>
		<link>http://metajack.wordpress.com/2008/07/02/xmpp-is-better-with-bosh/#comment-223</link>
		<dc:creator>metajack</dc:creator>
		<pubDate>Fri, 04 Jul 2008 05:57:15 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=62#comment-223</guid>
		<description>Very long packet length is not a limitation of BOSH, but is usually a restriction of the server.  The restriction is a very necessary one, and I&#039;ve written about this before here:
http://metajack.wordpress.com/2008/06/10/binary-data-is-xmpps-achilles-heel/

We use a custom web service to handle avatar uploads in both our native and web Chesspark clients.  Of course this doesn&#039;t solve the problem for all servers, but most users at Chesspark are using local accounts so far.

The real issue needs to be addressed in the specifications, and I hope to work on this soon.</description>
		<content:encoded><![CDATA[<p>Very long packet length is not a limitation of BOSH, but is usually a restriction of the server.  The restriction is a very necessary one, and I&#8217;ve written about this before here:<br />
<a href="http://metajack.wordpress.com/2008/06/10/binary-data-is-xmpps-achilles-heel/" rel="nofollow">http://metajack.wordpress.com/2008/06/10/binary-data-is-xmpps-achilles-heel/</a></p>
<p>We use a custom web service to handle avatar uploads in both our native and web Chesspark clients.  Of course this doesn&#8217;t solve the problem for all servers, but most users at Chesspark are using local accounts so far.</p>
<p>The real issue needs to be addressed in the specifications, and I hope to work on this soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Augustus Thoo</title>
		<link>http://metajack.wordpress.com/2008/07/02/xmpp-is-better-with-bosh/#comment-218</link>
		<dc:creator>Augustus Thoo</dc:creator>
		<pubDate>Fri, 04 Jul 2008 04:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=62#comment-218</guid>
		<description>There is one more downside to BOSH: very long XMPP packet length.

I tried sending a avatar+vcard update XMPP packet (20000+ bytes) using BOSH and got my session terminated by HTTP-Bind BOSH servlet running from my Openfire server.</description>
		<content:encoded><![CDATA[<p>There is one more downside to BOSH: very long XMPP packet length.</p>
<p>I tried sending a avatar+vcard update XMPP packet (20000+ bytes) using BOSH and got my session terminated by HTTP-Bind BOSH servlet running from my Openfire server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
