On Tue, Oct 28, 2008 at 9:07 PM, Pavel Shramov <[EMAIL PROTECTED]> wrote: > By the way one of the simpliest ways for RPC is to use HTTP transport. > It's have some limitations (e.g large overhead for small messages) but > also some benefits (e.g many libraries for performing HTTP calls and > simple proxying)
Speaking of ugly hacks, one of the intermediate versions of rpc I used were, actually, protocol buffers over xmlrpc. messages were serialized and then wrapped into xmlrpc.Binary -- This message represents the official view of the voices in my head. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
