Arnaud Simon wrote:
>
>
> If it also applies to receive(), and that's my interpretation, we can
> ack pseudo-asynchronously i.e. the next message transfer could carry an
> ack flag confirming that the broker has received the previous message
> acknowledgment. So we don't have to block on the ack before delivering
> the message to the receiver. Note that when the client lib is
> pre-fetching messages we only need to deliver the next message after the
> sync ack of the previous message has returned.
>
> Arnaud
>
>
Well, in the above, you're still effectively blocking on the ack, but in a
more roundabout way, since you can't deliver the next message until the ack
has reached the server then you are given notification of that by the next
message transfer- I think you're just moving the same issue from one place
to another.
--
View this message in context:
http://www.nabble.com/JMS-Acknowledgements-sent-asynchronously--tp17519565p17667716.html
Sent from the Qpid Developers mailing list archive at Nabble.com.
