<?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: Workaround to Flex SDK 3.4 Bug 22333 :: HTTPService Responders Are Called Twice&#8230;Here&#8217;s a Fix!</title>
	<atom:link href="http://www.webappsolution.com/wordpress/2009/09/29/workaround-to-flex-sdk-34-bug-22333-httpservice-responders-are-called-twiceheres-a-fix/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webappsolution.com/wordpress/2009/09/29/workaround-to-flex-sdk-34-bug-22333-httpservice-responders-are-called-twiceheres-a-fix/</link>
	<description>When you're in need of an appsolution</description>
	<pubDate>Fri, 18 May 2012 00:44:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ruprict</title>
		<link>http://www.webappsolution.com/wordpress/2009/09/29/workaround-to-flex-sdk-34-bug-22333-httpservice-responders-are-called-twiceheres-a-fix/comment-page-1/#comment-429</link>
		<dc:creator>Ruprict</dc:creator>
		<pubDate>Sat, 27 Feb 2010 13:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappsolution.com/wordpress/?p=551#comment-429</guid>
		<description>You just saved me a ton of time....thanks..</description>
		<content:encoded><![CDATA[<p>You just saved me a ton of time&#8230;.thanks..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Yahner</title>
		<link>http://www.webappsolution.com/wordpress/2009/09/29/workaround-to-flex-sdk-34-bug-22333-httpservice-responders-are-called-twiceheres-a-fix/comment-page-1/#comment-327</link>
		<dc:creator>Andrew Yahner</dc:creator>
		<pubDate>Mon, 23 Nov 2009 15:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappsolution.com/wordpress/?p=551#comment-327</guid>
		<description>I don't like adding event listeners to services.  What if your reuse your service and don't want other listeners...

better i think is this to attach a boolean to the TOKEN.  check the boolean states before performing the work in your result handler.

      var token:AsyncToken=_service.send();
      token.executed=false;

in the result handler, first statements should be:
      if (event.token.executed == false) {
        event.token.executed=true;
        //already fired (or firing);
        return;
      }</description>
		<content:encoded><![CDATA[<p>I don&#8217;t like adding event listeners to services.  What if your reuse your service and don&#8217;t want other listeners&#8230;</p>
<p>better i think is this to attach a boolean to the TOKEN.  check the boolean states before performing the work in your result handler.</p>
<p>      var token:AsyncToken=_service.send();<br />
      token.executed=false;</p>
<p>in the result handler, first statements should be:<br />
      if (event.token.executed == false) {<br />
        event.token.executed=true;<br />
        //already fired (or firing);<br />
        return;<br />
      }</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brianr</title>
		<link>http://www.webappsolution.com/wordpress/2009/09/29/workaround-to-flex-sdk-34-bug-22333-httpservice-responders-are-called-twiceheres-a-fix/comment-page-1/#comment-297</link>
		<dc:creator>brianr</dc:creator>
		<pubDate>Tue, 27 Oct 2009 21:27:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappsolution.com/wordpress/?p=551#comment-297</guid>
		<description>As a side note, make sure you remove your event listeners after the service has completed.

And Flex SDK 3.4.1.10084 fixes this issue so you can go back to the token best practice (which takes care of the tear down and removal of event handlers, etc).</description>
		<content:encoded><![CDATA[<p>As a side note, make sure you remove your event listeners after the service has completed.</p>
<p>And Flex SDK 3.4.1.10084 fixes this issue so you can go back to the token best practice (which takes care of the tear down and removal of event handlers, etc).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

