In case it's still useful, an example of creating an anonymous sender (used
here for the response part of a request/response interaction):
https://github.com/amqphub/equipage/blob/master/qpid-proton-python/respond.py#L44
(define
the anonymous sender)
Dear Robbie,
I'm very sorry for the late reply, but I had a few very busy days at work.
Thank you very much for your reply.
I will try to narrow down the issue and perform more tests, looking,
especially, if "high latency" peaks are always followed by "low latency"
measurements, as if transfers
I'd wonder whether if you are piling up lots of events for different
senders then it's potentially (again, I haven't used the Injector
bits, and Python isn't particularly my thing) just that many such
events are all piled up, and all processed before the resulting IO can
then be, effectively
Dear Robbie, dear Gordon,
Thank you very much for your replies and for your very useful and helpful
suggestions.
Looking better at the "db_send.py" and "tx_recv_interactive.py" examples, I
was finally able to code a working example by using the same loop as
before, but adding an EventInjector
On Thu, 16 Jul 2020 at 14:36, Francesco Raviglione
wrote:
>
> Dear Adrian,
> Thank you very much for your reply.
>
> I tried following your suggestion, by attempting to find a way to call an
> external function reading the data from an external source, and returning
> it when available.
>
>
On 15/07/2020 5:21 pm, Francesco Raviglione wrote:
I've seen that several examples are sending data which was
available/defined before the AMQP event loop is started.
However, I need to send data only when it becomes available from an
external process (for example by waiting for it on a Pipe,
On Fri, 17 Jul 2020 at 09:48, Francesco Raviglione
wrote:
>
> Dear Adrian,
> Thank you very much for your reply and for the pseudo-code.
>
> Unfortunately, I'm not sure if Python allows users to have a lower level
> control like when calling proactor_done() or proactor_wait() in C, but I
> will
Dear Adrian,
Thank you very much for your reply and for the pseudo-code.
Unfortunately, I'm not sure if Python allows users to have a lower level
control like when calling proactor_done() or proactor_wait() in C, but I
will surely try to understand if it is possible to implement a logic
similar
Hi,
For certain reasons I can't paste code here, so I'll try to give a
pseudo-code algorithm that worked for me with Proton-C. Don't know how much
control you have with the Python client.
--- Step 1: init ---
- Initialize proton/main event loop up to the moment you get the FLOW
event -->
Dear Adrian,
Thank you very much for your reply.
I tried following your suggestion, by attempting to find a way to call an
external function reading the data from an external source, and returning
it when available.
However, unfortunately, it seems to be slightly easier to control the
behaviour
Hi Francesco,
I achieved similar behavior but using Qpid Proton-C (AMQP send-only
program).
After initialiazing proton and getting the first FLOW event, I simply
"yield" main event loop control to an external/looping function that can
read from a different source and then send the same message
Dear all,
I'm trying to use the Python version of Qpid Proton to send data to an AMQP
1.0 broker.
I've seen that several examples are sending data which was
available/defined before the AMQP event loop is started.
However, I need to send data only when it becomes available from an
external process
12 matches
Mail list logo
