<?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 &#8220;Ajax&#8221; Update: Flex LiveCycle Data Services Goes Open-Source</title>
	<atom:link href="http://ajaxian.com/archives/ajax-in-flash-flex-livecycle-data-services-goes-open-source/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/ajax-in-flash-flex-livecycle-data-services-goes-open-source</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 11 Mar 2010 08:40:27 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: seanm</title>
		<link>http://ajaxian.com/archives/ajax-in-flash-flex-livecycle-data-services-goes-open-source/comment-page-1#comment-260010</link>
		<dc:creator>seanm</dc:creator>
		<pubDate>Fri, 14 Dec 2007 23:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3110#comment-260010</guid>
		<description>As others have commented, BlazeDS rivals &lt;a href=&quot;â€&quot; rel=&quot;nofollow&quot;&gt;Comet&lt;/a&gt;.   &lt;a href=&quot;â€http://www.knownow.comâ€&quot; rel=&quot;nofollow&quot;&gt;KnowNow&lt;/a&gt; itself was founded circa 2000 on the principles of HTTP real-time push; aka real-time content streaming.   KnowNow and others take a pure browser approach to the frontend contending that any dependency on the runtime components, even if itâ€™s as pervasive as Flash, is a limitation.  Flexibility in messaging format is also key to pervasive adoption as a general purpose pub/sub application platform. Juxtapose this against Adobe support for a single format that is designed to drive a single vendorâ€™s application use case needs.  Existing pub/sub push platforms such as our own allow for a variety of messaging  formats, both open and proprietary, such as JSON, RSS, Atom, other XML,  KnowNow JSobj, and perhaps adding &lt;a href=&quot;â€œhttp://download.macromedia.com/pub/labs/amf/amf3_spec_121207.pdfâ€&quot; rel=&quot;nofollow&quot;&gt;AMF&lt;/a&gt; to the mix sometime in the future too.  

Itâ€™s nice to see the endorsement from Adobe of the benefits of a standards-based browser RIA driven by â€œserver pushâ€  publish/subscribe services.  Adobe should be applauded for publishing the spec for AMF as well.  For more commentary about our viewpoint on this matter, see &lt;a href=&quot;â€&quot; rel=&quot;nofollow&quot;&gt;our viewpoint on our corporate blog&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>As others have commented, BlazeDS rivals <a href="â€" rel="nofollow">Comet</a>.   <a href="â€http://www.knownow.comâ€" rel="nofollow">KnowNow</a> itself was founded circa 2000 on the principles of HTTP real-time push; aka real-time content streaming.   KnowNow and others take a pure browser approach to the frontend contending that any dependency on the runtime components, even if itâ€™s as pervasive as Flash, is a limitation.  Flexibility in messaging format is also key to pervasive adoption as a general purpose pub/sub application platform. Juxtapose this against Adobe support for a single format that is designed to drive a single vendorâ€™s application use case needs.  Existing pub/sub push platforms such as our own allow for a variety of messaging  formats, both open and proprietary, such as JSON, RSS, Atom, other XML,  KnowNow JSobj, and perhaps adding <a href="â€œhttp://download.macromedia.com/pub/labs/amf/amf3_spec_121207.pdfâ€" rel="nofollow">AMF</a> to the mix sometime in the future too.  </p>
<p>Itâ€™s nice to see the endorsement from Adobe of the benefits of a standards-based browser RIA driven by â€œserver pushâ€  publish/subscribe services.  Adobe should be applauded for publishing the spec for AMF as well.  For more commentary about our viewpoint on this matter, see <a href="â€" rel="nofollow">our viewpoint on our corporate blog</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AndyB</title>
		<link>http://ajaxian.com/archives/ajax-in-flash-flex-livecycle-data-services-goes-open-source/comment-page-1#comment-259947</link>
		<dc:creator>AndyB</dc:creator>
		<pubDate>Thu, 13 Dec 2007 15:11:57 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3110#comment-259947</guid>
		<description>Or if there is going to be a single provider who open sources their stuff, it&#039;s still their responsibility to see it ported to more platforms IF THEY WANT TO SEE MORE PEOPLE USE IT.  Open sourcing something to try to get someone else to do your porting for you (or whatever we&#039;re calling Microsoft letting Novell (or whoever) write Moonlight as the portable version of Silverlight) may follow the letter of open source, but not the spirit.</description>
		<content:encoded><![CDATA[<p>Or if there is going to be a single provider who open sources their stuff, it&#8217;s still their responsibility to see it ported to more platforms IF THEY WANT TO SEE MORE PEOPLE USE IT.  Open sourcing something to try to get someone else to do your porting for you (or whatever we&#8217;re calling Microsoft letting Novell (or whoever) write Moonlight as the portable version of Silverlight) may follow the letter of open source, but not the spirit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joeri</title>
		<link>http://ajaxian.com/archives/ajax-in-flash-flex-livecycle-data-services-goes-open-source/comment-page-1#comment-259946</link>
		<dc:creator>Joeri</dc:creator>
		<pubDate>Thu, 13 Dec 2007 15:02:15 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3110#comment-259946</guid>
		<description>AMF3 is an object serialization protocol that is optimized for the flash client meant to shuttle data from server to flash client and vice versa without lengthy marshalling times (faster than JSON or XML). There&#039;s no point to &quot;support&quot; in the browser.

Their hope with opening it up is to see flash become more attractive as a development platform by defocusing their server solutions. They&#039;ll simply have to open source the client to really gain a foothold though.</description>
		<content:encoded><![CDATA[<p>AMF3 is an object serialization protocol that is optimized for the flash client meant to shuttle data from server to flash client and vice versa without lengthy marshalling times (faster than JSON or XML). There&#8217;s no point to &#8220;support&#8221; in the browser.</p>
<p>Their hope with opening it up is to see flash become more attractive as a development platform by defocusing their server solutions. They&#8217;ll simply have to open source the client to really gain a foothold though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Bond-Caron</title>
		<link>http://ajaxian.com/archives/ajax-in-flash-flex-livecycle-data-services-goes-open-source/comment-page-1#comment-259943</link>
		<dc:creator>Jonathan Bond-Caron</dc:creator>
		<pubDate>Thu, 13 Dec 2007 13:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3110#comment-259943</guid>
		<description>It&#039;s an interesting move, I looked into the AMF 3 Specification and from what I understand, it&#039;s a binary format (with limitations) highly tied with flash and adobe based technologies. I think their hope is too see browsers support AMF natively! The binary data exchange sounds like an open call for hackers to have even more fun on the Web!</description>
		<content:encoded><![CDATA[<p>It&#8217;s an interesting move, I looked into the AMF 3 Specification and from what I understand, it&#8217;s a binary format (with limitations) highly tied with flash and adobe based technologies. I think their hope is too see browsers support AMF natively! The binary data exchange sounds like an open call for hackers to have even more fun on the Web!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Snowcore</title>
		<link>http://ajaxian.com/archives/ajax-in-flash-flex-livecycle-data-services-goes-open-source/comment-page-1#comment-259936</link>
		<dc:creator>Snowcore</dc:creator>
		<pubDate>Thu, 13 Dec 2007 09:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3110#comment-259936</guid>
		<description>Yes, I agree with alp: there are troubles with this on iPhone :-(</description>
		<content:encoded><![CDATA[<p>Yes, I agree with alp: there are troubles with this on iPhone :-(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alp</title>
		<link>http://ajaxian.com/archives/ajax-in-flash-flex-livecycle-data-services-goes-open-source/comment-page-1#comment-259934</link>
		<dc:creator>alp</dc:creator>
		<pubDate>Thu, 13 Dec 2007 05:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3110#comment-259934</guid>
		<description>&gt;Many folks wonder why Ajax developers donâ€™t just use Flash
Perhaps because Flash isn&#039;t Ajax?  Doesn&#039;t run too well on the iPhone either :-P

Open sourcing around the edges does not change the fact that the player and its format are still proprietary and that there is only a single provider of that technology.  Some folks are comfortable with that, some aren&#039;t.</description>
		<content:encoded><![CDATA[<p>&gt;Many folks wonder why Ajax developers donâ€™t just use Flash<br />
Perhaps because Flash isn&#8217;t Ajax?  Doesn&#8217;t run too well on the iPhone either :-P</p>
<p>Open sourcing around the edges does not change the fact that the player and its format are still proprietary and that there is only a single provider of that technology.  Some folks are comfortable with that, some aren&#8217;t.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
