I also highly recommend Foolscap (http://foolscap.lothar.com/trac), which was designed as a next generation PB-like RPC protocol. Some advantages of Foolscap: * Security is built-in and easy to use. The security model of Foolscap is based on the object capability model and is really nice. If you need security (encryption+authentication) Foolscap is the way to go. PB can be made secure, but it is not straighforward. * Much better support for streaming large objects than PB or AMP has. We have used PB extensively as well though and if you don't need security or the ability to handle large objects, it it great. Bran On Wed, Nov 5, 2008 at 8:19 AM, Jean-Paul Calderone <exarkun@divmod.com> wrote:
On Wed, 5 Nov 2008 10:52:46 -0500, Black <python@blackslens.com> wrote:
I'm going to chime in here with a pretty general comment...
On Nov 5, 2008, at 1:18 AM, Blair Bethwaite wrote:
Guess I'll have to take a closer look at the Java implementation. Not sure why I didn't stumble across AMP before but looks promising...
I can probably guess why you didn't stumble across AMP, because it took me a long time to discover it as well. The problem is that ti isn't really discussed anywhere in the Twisted documentation (other than in the API description). It is, I think, one of the better kept secrets in the Twisted arsenal.
One reason for that is that AMP is about two years old; PB is at least 7, probably a little bit older.
Of course, it'd be great to have some howto-style documentation for AMP.
Jean-Paul
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python