<?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: Reusing XMLHttpRequest Without abort()</title>
	<atom:link href="http://ajaxian.com/archives/reusing-xmlhttprequest-without-abort/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/reusing-xmlhttprequest-without-abort</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Sri</title>
		<link>http://ajaxian.com/archives/reusing-xmlhttprequest-without-abort/comment-page-1#comment-110164</link>
		<dc:creator>Sri</dc:creator>
		<pubDate>Fri, 29 Sep 2006 14:38:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1049#comment-110164</guid>
		<description>We have another wierd issue when we try to abort a XHR before its complete, i.e when we close the window before the request comes back. After two times that we close the window, the XHR simply doesnt seem to respond. We need to shut down all the instances of IE to overcome this. Has anyone faced this before?</description>
		<content:encoded><![CDATA[<p>We have another wierd issue when we try to abort a XHR before its complete, i.e when we close the window before the request comes back. After two times that we close the window, the XHR simply doesnt seem to respond. We need to shut down all the instances of IE to overcome this. Has anyone faced this before?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adi Zholkover</title>
		<link>http://ajaxian.com/archives/reusing-xmlhttprequest-without-abort/comment-page-1#comment-60418</link>
		<dc:creator>Adi Zholkover</dc:creator>
		<pubDate>Sat, 05 Aug 2006 19:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1049#comment-60418</guid>
		<description>When I do XHR.abort() while XHR.readyState is 4, from within the onreadystate function, the XHR object gets &quot;stuck&quot; in readyState 4 and also runs the onreadystatechange function over and over again (with readyState=4).</description>
		<content:encoded><![CDATA[<p>When I do XHR.abort() while XHR.readyState is 4, from within the onreadystate function, the XHR object gets &#8220;stuck&#8221; in readyState 4 and also runs the onreadystatechange function over and over again (with readyState=4).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Russell</title>
		<link>http://ajaxian.com/archives/reusing-xmlhttprequest-without-abort/comment-page-1#comment-6002</link>
		<dc:creator>Alex Russell</dc:creator>
		<pubDate>Mon, 03 Apr 2006 22:17:19 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=1049#comment-6002</guid>
		<description>We&#039;ve done quite a bit of testing to remove leakage in Dojo, and the problem w/ XMLHTTP request objects (on IE anyway) always revolved around how the event handlers are set. The number of XMLHTTP objects created had little to no bearing on the leakage characteristics of the page.

The only thing that actually reduced leakage was handling state changes with a timer-based observer vs. directly attaching readystate handlers.

It&#039;s frustrating to see these &quot;what if!?!&quot; kinds of things get repeatedly posted when we&#039;ve &lt;a href=&quot;http://alex.dojotoolkit.org/?p=528&quot; title=&quot;already done the research&quot; rel=&quot;nofollow&quot;&gt;already done the research&lt;/a&gt; and found solutions.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve done quite a bit of testing to remove leakage in Dojo, and the problem w/ XMLHTTP request objects (on IE anyway) always revolved around how the event handlers are set. The number of XMLHTTP objects created had little to no bearing on the leakage characteristics of the page.</p>
<p>The only thing that actually reduced leakage was handling state changes with a timer-based observer vs. directly attaching readystate handlers.</p>
<p>It&#8217;s frustrating to see these &#8220;what if!?!&#8221; kinds of things get repeatedly posted when we&#8217;ve <a href="http://alex.dojotoolkit.org/?p=528" title="already done the research" rel="nofollow">already done the research</a> and found solutions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

