RubyAMF-0.9.8

K folks. One more huge bug fix. Plus a couple more helpers.

#Fix result set with Flash 9 issues. Result sets were being returned to Flash 9 as mx.remoting.RecordSet. Now it’s returned as fl.data.DataProvider. See this post for more info

#Added custom recordset_format header support. You can change the recordset format by adding the appropriate header to the netconnection. EX: service.addHeader(‘recordset_format:fl.data.DataProvider’,false,false); OR service.addHeader(‘recordset_format:mx.remoting.RecordSet’,false,false);

#Made sure the _explicitType member variable isn’t being written in the actionscript object when serializing AF3 or AMF0

#added db_error_logger helper class. Use for easily logging errors in services

#added error_notification class. Use for sending emails when errors happen, Note this is just stub code for now

Have a look at the code profiling that’s been going on to optimize RubyAMF. Finding bottlenecks, optimizing everything I can. There have been a number of requests for a C extension, and yes let me tell you that it will happen. But I figured before I put all my efforts into that I wanted to make the existing ruby code base bug free and as fast as possible. That way it will always be blazing fast.

I’ve got a few things left to do before considering this for a version 1.0 final release:

1. Mongrel Daemonizing. (Something wrong with mongrel daemon right now)
2. Windows services
3. Stress testing the crap out of each server

That’s it for now. Download it

aaron said,

June 28, 2007 @ 23:18

Forgot one on my list of things todo. Zlib compressing the response for browsers that accept gzip deflate.

aaron said,

July 2, 2007 @ 17:37

Using the addHeader function is slighty different now.

addHeader(‘recordset_format’,false,’[fl.data.DataProvider|mx.remoting.RecordSet']);

RSS feed for comments on this post · TrackBack URI

Leave a Comment