It seems to me that this is something that can be done completely outside of Thrift (and we have done it at least once at Facebook).
Could you write a wiki page about how you did it? Thanks.
Currently, it is not possible to use the same connection for multiple simultaneous requests, but the concept of a client pool should still
I do not want to have simultaneous requests over one connection, because I assume building a transport that only supports serialized requests is much easier. But as I said before I have no experience in writing protocols, so I could be wrong.
work. If this is done in a general way, I'd be happy to include it in the base Thrift distribution.
I am currently thinking in the direction of adding a TProtocol wrapper that will add a service identifier prefix to each message name. On the server side the message name will be split so the service and the function can be looked up.
I would like to have some input about what the best way would be to handle error conditions: timeouts, corrupt streams, etc.
-- Kind regards, Johan Stuyts
