Sent: Monday, November 6, 2023 4:07 PM
To: users@qpid.apache.org
Subject: RE: external event loop
Hi,
So all working fine with Connection_driver and an external event loop.
However, when trying to add a 're-connect' feature, the connection_driver based
client is unresponsive.
Details:
Hi,
So all working fine with Connection_driver and an external event loop.
However, when trying to add a 're-connect' feature, the connection_driver based
client is unresponsive.
Details:
1. When the server fails abruptly, the loss of transport is detected by a
socket recv on the client.
in Heartbeats ?
>
> Thanks,
> - Tom
>
> From: Tom Crowe
> Sent: Wednesday, October 25, 2023 5:44 PM
> To: users@qpid.apache.org
> Subject: RE: external event loop
>
> Thanks Cliff for your helpful answer to this topic way back on June 30th.
>
> "If you
Hi,
Any feedback on this point... for connection_driver, must I call tick() if
I'm not interested in Heartbeats ?
Thanks,
- Tom
From: Tom Crowe
Sent: Wednesday, October 25, 2023 5:44 PM
To: users@qpid.apache.org
Subject: RE: external event loop
Thanks Cliff for your helpful answer to
haps I don't need to call the tick() function at all ?
Or does tick() service other needs e.g. message aging in queues OR timeouts
related to settlement OR something else ?
Thanks.
From: Tom Crowe
Sent: Friday, June 30, 2023 11:09 AM
To: users@qpid.apache.org
Subject: RE: external event loo
Hi Tom,
As a further note to whatever you have found so far...
The recommended route would be for you to retain your existing code
based on proton::container, and allow it to run with its own dedicated
thread (or threads) using its own epoll loop and let Proton manage the
sockets for the AMQP con
Discovered that search function on mail lists is returning hits, albeit hidden
from view.
Found enough info to work from.
Thanks,
- Tom
On 2023/06/28 14:12:14 Tom Crowe wrote:
> Hi,
> I have a working prototype with qpid proton c++ v0.37 consuming an amqps
> 1.0 data feed.
>
> Next, I would li
