<?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/"
		>
<channel>
	<title>Comments on: Overhauling the XMLHttpRequest documentation</title>
	<atom:link href="http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/</link>
	<description>Bits on the rampage: Eric Shepherd's blog.</description>
	<lastBuildDate>Wed, 01 Feb 2012 14:15:55 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Vladimir Dzhuvinov</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82871</link>
		<dc:creator>Vladimir Dzhuvinov</dc:creator>
		<pubDate>Wed, 29 Oct 2008 06:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82871</guid>
		<description>Leaks as in &quot;memory leaks&quot;? :-?

I searched bugzilla for &quot;xmlhttprequest + memory + leak&quot; and couldn&#039;t find any applicable confirmed bugs.

If we put aside good programming practice for a moment, are there really bad things lurking in synchronous XHR?</description>
		<content:encoded><![CDATA[<p>Leaks as in &#8220;memory leaks&#8221;? :-?</p>
<p>I searched bugzilla for &#8220;xmlhttprequest + memory + leak&#8221; and couldn&#8217;t find any applicable confirmed bugs.</p>
<p>If we put aside good programming practice for a moment, are there really bad things lurking in synchronous XHR?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sheppy</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82862</link>
		<dc:creator>sheppy</dc:creator>
		<pubDate>Fri, 24 Oct 2008 18:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82862</guid>
		<description>Vladimir Dzhuvinov --

Firefox 3 no longer blocks the UI when handling synchronous XMLHttpRequests, because otherwise there&#039;s no way for the user to terminate one that&#039;s locked up.  It&#039;s strongly recommended that you avoid using synchronous requests, because they can leak in various ways, and asynchronous just isn&#039;t that much more complicted.</description>
		<content:encoded><![CDATA[<p>Vladimir Dzhuvinov &#8211;</p>
<p>Firefox 3 no longer blocks the UI when handling synchronous XMLHttpRequests, because otherwise there&#8217;s no way for the user to terminate one that&#8217;s locked up.  It&#8217;s strongly recommended that you avoid using synchronous requests, because they can leak in various ways, and asynchronous just isn&#8217;t that much more complicted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vladimir Dzhuvinov</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82861</link>
		<dc:creator>Vladimir Dzhuvinov</dc:creator>
		<pubDate>Fri, 24 Oct 2008 07:10:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82861</guid>
		<description>Sheppy, thank you for the clarification :)

Today I was trying to find out why the FF3 UI doesn&#039;t freeze on blocking XHR calls (as with earlier versions). I&#039;m developing a standalone xulrunner app and it seems that now the main argument for using asynchronous XHR calls - preventing UI lock-up - is gone. Has synchronous XHR become &quot;safe&quot; now?

Strangely, I couldn&#039;t find any info on this programming issue! It&#039;s important to me because it gives me an option to simplify programming throughout the whole application.</description>
		<content:encoded><![CDATA[<p>Sheppy, thank you for the clarification :)</p>
<p>Today I was trying to find out why the FF3 UI doesn&#8217;t freeze on blocking XHR calls (as with earlier versions). I&#8217;m developing a standalone xulrunner app and it seems that now the main argument for using asynchronous XHR calls &#8211; preventing UI lock-up &#8211; is gone. Has synchronous XHR become &#8220;safe&#8221; now?</p>
<p>Strangely, I couldn&#8217;t find any info on this programming issue! It&#8217;s important to me because it gives me an option to simplify programming throughout the whole application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sheppy</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82852</link>
		<dc:creator>sheppy</dc:creator>
		<pubDate>Fri, 17 Oct 2008 14:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82852</guid>
		<description>Vladimir: The callback handler runs on the GUI thread; otherwise you wouldn&#039;t have access to the DOM.</description>
		<content:encoded><![CDATA[<p>Vladimir: The callback handler runs on the GUI thread; otherwise you wouldn&#8217;t have access to the DOM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sheppy</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82851</link>
		<dc:creator>sheppy</dc:creator>
		<pubDate>Fri, 17 Oct 2008 14:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82851</guid>
		<description>Yes, these are 16 bit characters, which is why the high byte gets stripped off to create bytes.</description>
		<content:encoded><![CDATA[<p>Yes, these are 16 bit characters, which is why the high byte gets stripped off to create bytes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boemer</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82850</link>
		<dc:creator>boemer</dc:creator>
		<pubDate>Fri, 17 Oct 2008 13:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82850</guid>
		<description>seems we&#039;re talking about 16bits chars... (utf8?)</description>
		<content:encoded><![CDATA[<p>seems we&#8217;re talking about 16bits chars&#8230; (utf8?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boemer</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82849</link>
		<dc:creator>boemer</dc:creator>
		<pubDate>Fri, 17 Oct 2008 13:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82849</guid>
		<description>I would remove the high-order bit instead of the byte, I guess, you don&#039;t have much left if you remove the whole byte of a character...

SendAsBinary: The request body as a DOM string.  This data is converted to a string of single-byte characters by truncation (removing the high-order !!!byte!!! of each character).</description>
		<content:encoded><![CDATA[<p>I would remove the high-order bit instead of the byte, I guess, you don&#8217;t have much left if you remove the whole byte of a character&#8230;</p>
<p>SendAsBinary: The request body as a DOM string.  This data is converted to a string of single-byte characters by truncation (removing the high-order !!!byte!!! of each character).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vladimir Dzhuvinov</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82848</link>
		<dc:creator>Vladimir Dzhuvinov</dc:creator>
		<pubDate>Fri, 17 Oct 2008 06:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82848</guid>
		<description>Great, great, great! The new version is a lot clearer!

I&#039;ve got a question though: the callback handler - does it run on the spawned thread or on the GUI thread?</description>
		<content:encoded><![CDATA[<p>Great, great, great! The new version is a lot clearer!</p>
<p>I&#8217;ve got a question though: the callback handler &#8211; does it run on the spawned thread or on the GUI thread?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Mielczarek</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82847</link>
		<dc:creator>Ted Mielczarek</dc:creator>
		<pubDate>Fri, 17 Oct 2008 02:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82847</guid>
		<description>Looks good! I wrote the original page on kb.mozillazine.org a while back, and copied it to MDC at some point. It wasn&#039;t great, but it was better than nothing. Now it&#039;s well-organized and useful!</description>
		<content:encoded><![CDATA[<p>Looks good! I wrote the original page on kb.mozillazine.org a while back, and copied it to MDC at some point. It wasn&#8217;t great, but it was better than nothing. Now it&#8217;s well-organized and useful!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fabian</title>
		<link>http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/comment-page-1/#comment-82846</link>
		<dc:creator>fabian</dc:creator>
		<pubDate>Fri, 17 Oct 2008 00:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2008/10/16/overhauling-the-xmlhttprequest-documentation/#comment-82846</guid>
		<description>ah nice. thanks.

I hated it not having a good documentation about the XHR implementation in Mozilla. Also multipart! great! &lt;3</description>
		<content:encoded><![CDATA[<p>ah nice. thanks.</p>
<p>I hated it not having a good documentation about the XHR implementation in Mozilla. Also multipart! great! &lt;3</p>
]]></content:encoded>
	</item>
</channel>
</rss>

