On 05/28/2013 11:26 AM, Wolfgang Keller wrote: >> Please give me an example of a "suitable transport layer for a RPC >> protocol". > > I won't give you an example, but just some very basic criteria: > > - It must be very efficient for very small "datagrams"
I won't argue for XML here, but sometimes space efficiency is simply a premature optimization. > - It must provide connections How would you do this? Connections can and do get dropped regularly. To rebuild connections you need another layer to track them. > - For asynchronous programming it must provide for callbacks What do you mean by this? A transport layer has nothing to do with callbacks. All a client can do is make the call, and wait for the answer. The client library can make it look asynchronous of course. And I suppose one could implement an RPC system using UDP where answer packets are dispatched as they come in. -- http://mail.python.org/mailman/listinfo/python-list
