On Wed, May 6, 2009 at 11:53 AM, David Reiss <[email protected]> wrote:
> > 2) If not, roughly how much work is involved in doing such a port from > > scratch ? In the end, I need to do this or write my own RPC protocol. > I'd > > rather support the Thrift project if it's doable. Is a partial port > > possible ? It seems so. Even a basic port of the core transport stuff > > would be fine. Don't need Flash based servers !! > I think the hardest part is the [de]serialization code. You'd have to port > about 2000 lines from another generator (probably Java?) to generate your > language. Partial ports (no processor or server, e.g.) are definitely > acceptable. > An alternative route is to use Thrift only for its RPC description capability, and skip serialization altogether. Amie Street has an as3 generator that does this, and simply creates classes that use normal AMF to speak to a server. It's then up to the server to implement the interface using whichever AMF gateway they so choose. The generator is here: http://thrift-rpc.org/?p=thrift.git;a=blob;f=compiler/cpp/src/generate/t_as3_generator.cc;h=33520bbcf842687e1dc8cab7ada336c8327272f5;hb=1aaeaebebd5ba9acff446abc016333a8767a8b44 You should be able to pull the relevant commits out of that git branch. I'll ping Aaron Myers, who wrote this code, and see if there have been any further improvements since the last version I pushed. -Todd
