thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Reiss <dre...@facebook.com>
Subject Re: Non-standard transports
Date Sun, 07 Jun 2009 03:37:43 GMT
I'm not sure I understand your exact use case, but it is fairly easy
in Thrift to swap out the standard transport implementations for your
own.  It sounds like your use case is fairly similar to the THttpClient,
which is a TTransport that sends messages as http requests.

--David

Joshua Kramer wrote:
> Hello,
> 
> Is there any support, in either Python or C++, for servers with 
> non-standard transports?
> 
> For example, suppose I have a message.  I would like to call some method 
> on the message that would automatically determine its Operation, 
> dispatch the method call, and give me a message with the return value.
> 
> I am using the Apache QPid for all of my messages.  Currently I am using 
> Google Protocol Buffers to do calls between Python clients and servers 
> via Apache QPid.  My server daemon receives a message, deserializes it 
> via PB, dispatches to the correct method, and re-serializes the return 
> object to send back to the QPid server.  The exception handling and 
> dispatch provided by Thrift is appealing...
> 
> Cheers,
> -JK

Mime
View raw message