qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Conway <acon...@redhat.com>
Subject Re: svn commit: r1642720 - in /qpid/trunk/qpid/cpp/src/qpid/messaging/amqp: AddressHelper.h ConnectionContext.cpp ReceiverContext.cpp ReceiverContext.h SessionContext.cpp SessionContext.h
Date Wed, 03 Dec 2014 21:19:34 GMT
I have a new and satisfyingly simpler fix for this that I think covers all the points raised
on the mailing list. Will commit as soon as apache SVN is back in action.

----- Original Message -----
> On 12/02/2014 07:57 PM, Rob Godfrey wrote:
> >  From a protocol perspective all transfers need to be settled.  Does the
> > broker support the "send settled" mode?
> 
> Yes
> 
> > The sane thing for browsing
> > consumers would be to suggest to the broker that it should use
> > "snd-settle-mode" of settled.
> 
> Yes, that would I think be relatively straightforward.Its what is done
> if the link is configured to be 'unreliable'.
> 
> >  The client would only need to
> > (automatically, behind the scenes) settle transfers if the broker opted not
> > to use that settlement mode.
> 
> I think proton may require it to be locally settled anyway, just so it
> can be freed.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message