Ted Patrick - Demos & MAX @ Adobe Systems
Note: This is the personal blog of Ted Patrick. The opinions and statements voiced here are my own.
AmFast Remoting for Python
DIGG IT!
6
Comments
Published
Monday, March 23, 2009
at
9:48 AM
.
AmFast is a new AMF0/AMF3 encoder/decoder for Python.• AmFast's core encoder and decoder are written in C, so it's around 18x faster than PyAmf.
• The encoder and decoder accept user-defined Python objects that allow customization of the encoding/decoding process.
• Supports custom class mapping.
• Supports remoting with NetConnection and RemoteObject.
• Remoting headers can be exposed to callable targets to allow for quick implementation of authentication and other AMF features that rely on headers.
• Supports data persistence with SQLAlchemy, including remotely-loadable lazy-loaded attributes.
• Supports Actionscript code generation for mapped classes.
Project Page
It is really great to see how opening the AMF and RTMP protocols have really improved integration with server languages. To exchange objects makes development so much easier.
Cheers,
Ted :)
6 Responses to “AmFast Remoting for Python”
Post a CommentWhere to find me:
Ted on Twitter - @AdobeTed
Ted on Adobe Groups
Ted on LinkedIn
Ted on Facebook
Ted at Adobe
Latest
- Flex BugQuash - Live from Seattle or Online via Co...
- Adobe MAX 2009 - Call for Sessions and Labs
- Flex 3.3 Released!
- Facebook and the Flash Platform ESeminar
- Headed towards the finish line, Safari 4 takes the...
- Adobe on Twitter
- 20% off at Adobe Store for NA User Group Members
- Eclipse E4 M1 SWT: JAVA to AS3
- MindJet Launches MindManager Web ( 100% Flash mind...
- New Apps on Adobe Groups: Jobs, Calendar, Messagin...
Lists
Links
Jobs
Flex JobsArchives
- May 2003
- June 2003
- July 2003
- August 2003
- September 2003
- October 2003
- November 2003
- December 2003
- January 2004
- February 2004
- March 2004
- April 2004
- May 2004
- June 2004
- July 2004
- August 2004
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- February 2005
- March 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- October 2006
- November 2006
- December 2006
- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007
- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- October 2008
- November 2008
- December 2008
- January 2009
- February 2009
- March 2009
- April 2009
- May 2009
- June 2009
- July 2009
- August 2009
- September 2009
- October 2009
- November 2009
As of my understanding the RTMP protocol and AMF messages are not open yet. It's only announced on devnet to be opened soon: http://www.adobe.com/devnet/rtmp/
Or have I missed something important? In case there is an official specification available this would really help for a project where I'm working on. As for now we're reverse engineering the protocol for a complete C# implementation.
Anyway, good to hear the news about AmFast!
The AMF spec was released under OSS with the Blaze DS product release. This has created many open source version of AMF Remoting compatible with just about every server side language out there.
Ted :)
Hi Ted,
You maybe interested a collection of OSGi bundles that I put together that also allow AMF3 based remoting from Flex clients to OSGi services:
http://www.arum.co.uk/amf3osgi.php
The implementation of the AMF3 handling is actually based on GraniteDS AMF3 code, sorry ;) but it is a completely separate beast and doesn't provide 'Data Services'.
Eventually I'll be porting it support the new distributed OSGi specification.
Cheers,
Chris
is it 18x faster than cPyAMF?
http://blog.pyamf.org/archives/introducing-cpyamf
Yes, AmFast is at least 18x faster than cPyAmf, currently PyAmf will use it's C encoder/decoder only for a couple of types (ints and strings I believe). AmFast uses C for everything, including references, so it is much faster. The only thing AmFast is missing right now is the ability to act as a client, but that shouldn't be too hard to add if you need it.
AmFast is ~18x faster than cPyAmf. cPyAmf only encodes/decodes a couple of types (ints and strings I think) with it's C-extensions. AmFast encodes/decodes all types in C. 18x is just an average, some object graphs will be quicker, some slower.