
<?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: Flash Remoting Data Management</title>
	<atom:link href="http://blog.nobien.net/2008/09/12/flash-remoting-data-managment/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nobien.net/2008/09/12/flash-remoting-data-managment/</link>
	<description>A nerd blog about nerdy things by ... nerdy guys?</description>
	<lastBuildDate>Tue, 11 Oct 2011 21:59:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Clint</title>
		<link>http://blog.nobien.net/2008/09/12/flash-remoting-data-managment/comment-page-1/#comment-4103</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Mon, 15 Sep 2008 01:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nobien.net/?p=79#comment-4103</guid>
		<description>For what it&#039;s worth I&#039;m running into the exact same sort of dilemmas with my approach to data management and communication with AMFPHP.

I&#039;d certainly be interested in any revelations or perhaps even design patterns that emerge from working with AMFPHP.

Right now I have a DataModel singleton that handles both the communication with AMFPHP and the local storage of variables used throughout the application.  

My main problems arise from working out who (which class) should be calling and listening for returned data.  

If the DataModel calls and listens for data returns, you have to then dispatch an event (sometimes a custom event) so that the class that originally requested the data can be notified when the data is available.  

Seems to be a lot of doubling up of listeners for the same returned data event.</description>
		<content:encoded><![CDATA[<p>For what it&#8217;s worth I&#8217;m running into the exact same sort of dilemmas with my approach to data management and communication with AMFPHP.</p>
<p>I&#8217;d certainly be interested in any revelations or perhaps even design patterns that emerge from working with AMFPHP.</p>
<p>Right now I have a DataModel singleton that handles both the communication with AMFPHP and the local storage of variables used throughout the application.  </p>
<p>My main problems arise from working out who (which class) should be calling and listening for returned data.  </p>
<p>If the DataModel calls and listens for data returns, you have to then dispatch an event (sometimes a custom event) so that the class that originally requested the data can be notified when the data is available.  </p>
<p>Seems to be a lot of doubling up of listeners for the same returned data event.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

