In my RabbitMQ implementation the producer (client) connects to the
broker, optionally to an exchange, and always creates a private reply queue
for RPC replies. The consumer (server) connects to the broker, optionally
to an exchange, and always creates a request queue. I have the message
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
