<?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: What we need is Ruby AMF</title>
	<atom:link href="http://blog.xsive.co.nz/archives/124/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.xsive.co.nz/archives/124</link>
	<description>Weblog for X$!Ve.co.nz, Campbell Anderson Flex Developer</description>
	<lastBuildDate>Wed, 04 Aug 2010 08:50:19 +1200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Aaron Smith</title>
		<link>http://blog.xsive.co.nz/archives/124/comment-page-1#comment-100159</link>
		<dc:creator>Aaron Smith</dc:creator>
		<pubDate>Fri, 18 May 2007 14:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xsive.co.nz/archives/124#comment-100159</guid>
		<description>This is a way late comment post but check out rubyamf.org</description>
		<content:encoded><![CDATA[<p>This is a way late comment post but check out rubyamf.org</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark  Piller</title>
		<link>http://blog.xsive.co.nz/archives/124/comment-page-1#comment-10285</link>
		<dc:creator>Mark  Piller</dc:creator>
		<pubDate>Wed, 02 Aug 2006 16:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xsive.co.nz/archives/124#comment-10285</guid>
		<description>We&#039;re working on an open-source implementation of our Flash Remoting gateway (WebORB) for Ruby on Rails. As of now (08/02/06), we have a working version of the product that handles invocations of Ruby objects and can pass primitives, strings, arrays and complex types as method arguments or return types. We&#039;re hoping to have a GA release in Q3 of this year. The ultimate goal is to provide an implementation of Flex Data Services-like functionality for Rails. Some of the core FDS features would probably be available for a fee, but the remoting support for AMF0 and AMF3 will be free and open source.</description>
		<content:encoded><![CDATA[<p>We&#8217;re working on an open-source implementation of our Flash Remoting gateway (WebORB) for Ruby on Rails. As of now (08/02/06), we have a working version of the product that handles invocations of Ruby objects and can pass primitives, strings, arrays and complex types as method arguments or return types. We&#8217;re hoping to have a GA release in Q3 of this year. The ultimate goal is to provide an implementation of Flex Data Services-like functionality for Rails. Some of the core FDS features would probably be available for a fee, but the remoting support for AMF0 and AMF3 will be free and open source.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Lapshin</title>
		<link>http://blog.xsive.co.nz/archives/124/comment-page-1#comment-5731</link>
		<dc:creator>Max Lapshin</dc:creator>
		<pubDate>Fri, 30 Jun 2006 07:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xsive.co.nz/archives/124#comment-5731</guid>
		<description>Hi, I&#039;ve implemented encoder/decoder of amf packets. It seems, that the same work is done by amf4r. I&#039;ll try to merge with them, however, I can read and write amf now.</description>
		<content:encoded><![CDATA[<p>Hi, I&#8217;ve implemented encoder/decoder of amf packets. It seems, that the same work is done by amf4r. I&#8217;ll try to merge with them, however, I can read and write amf now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Campbell</title>
		<link>http://blog.xsive.co.nz/archives/124/comment-page-1#comment-1189</link>
		<dc:creator>Campbell</dc:creator>
		<pubDate>Wed, 07 Jun 2006 21:13:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xsive.co.nz/archives/124#comment-1189</guid>
		<description>Hey Kevin, Cheers for the comment, The main problem is the application loads the data for a page of images and then the thumbs of those images. Thats a big hit up front when the swf loads. So while I really like the idea of loading the data gracefully like that it doesnt fit the bill for this instance. I have read through Tinks blog and found that the documentation process for adobe is pretty much when the developer has time so I suspect the AMF spec isnt to well fleshed out, and not open to public. But I do love xml as a data source....its just so easy now.Jono who made the SWFZ engine has a zip unloader which  will be nice and I think I will endevour to get gzip compression turned on on the server.</description>
		<content:encoded><![CDATA[<p>Hey Kevin, Cheers for the comment, The main problem is the application loads the data for a page of images and then the thumbs of those images. Thats a big hit up front when the swf loads. So while I really like the idea of loading the data gracefully like that it doesnt fit the bill for this instance. I have read through Tinks blog and found that the documentation process for adobe is pretty much when the developer has time so I suspect the AMF spec isnt to well fleshed out, and not open to public. But I do love xml as a data source&#8230;.its just so easy now.Jono who made the SWFZ engine has a zip unloader which  will be nice and I think I will endevour to get gzip compression turned on on the server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Hoyt</title>
		<link>http://blog.xsive.co.nz/archives/124/comment-page-1#comment-1188</link>
		<dc:creator>Kevin Hoyt</dc:creator>
		<pubDate>Wed, 07 Jun 2006 19:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xsive.co.nz/archives/124#comment-1188</guid>
		<description>Interesting solution to a specific problem.  An approach that I&#039;ve seen in the Flex world is to &quot;pre-fetch&quot; common data.  The idea is that once the application has rendered and has enough data to get started, you can make additional calls for related data in the background.  This requires a certain knowledge of what the common &quot;moves&quot; are by end-users.  It also disregards client memory usage, but can be pretty darn elegant when bandwidth is at a minimum.</description>
		<content:encoded><![CDATA[<p>Interesting solution to a specific problem.  An approach that I&#8217;ve seen in the Flex world is to &#8220;pre-fetch&#8221; common data.  The idea is that once the application has rendered and has enough data to get started, you can make additional calls for related data in the background.  This requires a certain knowledge of what the common &#8220;moves&#8221; are by end-users.  It also disregards client memory usage, but can be pretty darn elegant when bandwidth is at a minimum.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Wanja</title>
		<link>http://blog.xsive.co.nz/archives/124/comment-page-1#comment-1185</link>
		<dc:creator>Daniel Wanja</dc:creator>
		<pubDate>Wed, 07 Jun 2006 14:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xsive.co.nz/archives/124#comment-1185</guid>
		<description>Over a year ago I played integrating a flash/flex front-end with a ruby on rails application using AMF. We decided not to move forward using this approach and create a &#039;plain&#039; old Rails app instead. However we published some of the work on http://flexonrails.com, we basically created a wrapper on top of AMF4R http://rubyforge.org/projects/amf4r/.  Note that our code certainly would not work with the current version of Rails and didn&#039;t work at that time on OSX due to some big endian issues in AMF4R. Altought AMF is a very efficient was of exchanging data between client and server, I would for now use a RESTfull approach (xml), on another project I use JSON which is very basic but work pretty well.</description>
		<content:encoded><![CDATA[<p>Over a year ago I played integrating a flash/flex front-end with a ruby on rails application using AMF. We decided not to move forward using this approach and create a &#8216;plain&#8217; old Rails app instead. However we published some of the work on <a href="http://flexonrails.com" rel="nofollow">http://flexonrails.com</a>, we basically created a wrapper on top of AMF4R <a href="http://rubyforge.org/projects/amf4r/" rel="nofollow">http://rubyforge.org/projects/amf4r/</a>.  Note that our code certainly would not work with the current version of Rails and didn&#8217;t work at that time on OSX due to some big endian issues in AMF4R. Altought AMF is a very efficient was of exchanging data between client and server, I would for now use a RESTfull approach (xml), on another project I use JSON which is very basic but work pretty well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Campbell</title>
		<link>http://blog.xsive.co.nz/archives/124/comment-page-1#comment-1184</link>
		<dc:creator>Campbell</dc:creator>
		<pubDate>Wed, 07 Jun 2006 13:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xsive.co.nz/archives/124#comment-1184</guid>
		<description>For those interested found Yannick has made a pure ruby AMF server here:
http://osflash.org/rtmp_os#yannick_s_ruby_build</description>
		<content:encoded><![CDATA[<p>For those interested found Yannick has made a pure ruby AMF server here:<br />
<a href="http://osflash.org/rtmp_os#yannick_s_ruby_build" rel="nofollow">http://osflash.org/rtmp_os#yannick_s_ruby_build</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chuck</title>
		<link>http://blog.xsive.co.nz/archives/124/comment-page-1#comment-1183</link>
		<dc:creator>chuck</dc:creator>
		<pubDate>Wed, 07 Jun 2006 12:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xsive.co.nz/archives/124#comment-1183</guid>
		<description>Not too long ago I heard about a project on SourceForge called AMF4R.  Apparently it has moved to RubyForge: http://rubyforge.org/projects/amf4r/</description>
		<content:encoded><![CDATA[<p>Not too long ago I heard about a project on SourceForge called AMF4R.  Apparently it has moved to RubyForge: <a href="http://rubyforge.org/projects/amf4r/" rel="nofollow">http://rubyforge.org/projects/amf4r/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
