On Tue, Jul 13, 2021 at 12:23 PM rahul.sin...@morganstanley.com <rahul.sin...@morganstanley.com> wrote: > I am using qpid-cpp-1.39.0 and want to create multiple topics and handle > incoming data in the most efficient way. What I have understood is that the > qpid::messaging::Connection, Session and Receiver are all created in the > application thread. When we try to fetch data from the Receiver, this is also > processed in the application thread. But under the hood, it sounds like the > Session might be communicating with the broker in a different thread and > buffering up the incoming data for appropriate receivers to fetch them. I am > inferring this after reading the in line comments for Receiver::fetch() > method which states that "this method will check with the server that there > is no message for the subscription this receiver is serving before returning > false."
Correct. There is an IO thread that does all the sending and receiving of data. > Is there a way we can get the thread Id or any Callback from it so that we > can determine the thread id. There is no callback. You could get the thread id from pstack output. Why do you need it? (If you prefer a callback style of API, look at the QPid proton c++ library). > Also is it correct to assume there is only 1 such thread per Session which is > getting data from the other end? There is one IO thread per connection. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
