Gotcha, just wanted to make sure you weren't expecting the API to do more
than it was actually doing. ;-)
--Rafael
On Thu, Feb 20, 2014 at 11:54 AM, Shearer, Davin wrote:
> Hi Rafael,
>
> Duplicates are acceptable, message loss is not. I'll handle any duplicates
> outside of messaging.
>
Hi Rafael,
Duplicates are acceptable, message loss is not. I'll handle any duplicates
outside of messaging.
Just FYI, what you are doing isn't strictly speaking transactional. If your
client dies after it has sent the processed message to the outbox, but
before it has acknowledged the message from the inbox, then the message
from the inbox will end up getting processed again and you may therefore
see a d
Ok, I think I've found the solution to this.
I want to treat the period from recv to send to be transactional. So
here's what I've got:
pn_messenger_t * pMessenger...
pn_message_t * pMessage(pn_message());
... recv side ...
/* Set incoming window to 1 message */
pn_messenger_set_incoming_windo
Hello,
I have two queues and a few services that receive from one queue (call it
"inbox") process the data received, then sends the processed data to the
other queue (call it "outbox"). Is there a sane way using proton to fetch
the content of the message from the "inbox", process the data, send t
