Hi, > Thrift transport (at least in C++) does not have a concept of a > transport hint that could carry through the processor for each request.
Correct. Because nobody needs it for pure and simple RPC & serialization which is the scope where Thrift operates. There is no need to carry a correlation ID around unless you need it. We than make it part of the messages we send back and fort. I would love to use THeader for stuff like that, but it's only available for C++ right now. > I am working on Message Bus support for Apache Thrift. Currently I am in > the middle of developing RabbitMQ support and then I will be looking into > Kafka. Specifically, with Rabbit and 0MQ and ActiveMQ I dealt with a while ago, I aloy played with some other systems like MSMQ and Rebus (a NService Bus clone). But before we got down to the matter, could you share an idea about the generalities of the implementation idea? Have fun, JensG -----Ursprüngliche Nachricht----- From: James E. King III Sent: Friday, July 6, 2018 3:54 PM To: dev@thrift.apache.org Subject: Transport Hints - Message identity and routing I am working on Message Bus support for Apache Thrift. Currently I am in the middle of developing RabbitMQ support and then I will be looking into Kafka. I found that in order to receive requests and route replies properly, I need a way to identify where the request came from when sending the reply. Thrift transport (at least in C++) does not have a concept of a transport hint that could carry through the processor for each request. These hints would be entirely opaque and only useful or understandable to the layer that inserted them. They also would not likely be useful to stream based transports, but I believe they are necessary for message-based transports to work properly. There's a bit of an impedance mismatch there, however any use of a message bus really requires framed transport which separates messages anyway. This is something I will be looking into soon, so if anyone has any thoughts about it please let me know. - Jim
