>From an AMQP 1.0 perspective, the broker really shouldn't need telling. The intention was that a container may decide to batch information it has on hand, but it should always be "prompt" in informing its peers of disposition changes. So its valid to wait until you've finished process a batch of incoming stuff before generating an optimised set of disposition state, but not to hold onto the data on the hope of hearing more at some indeterminate point in the future and only informing your partner of the dispositions at that time.
-- Rob On 15 April 2014 14:44, Pavel Moravec <[email protected]> wrote: > Hello, > I have spotted a performance-impacting lack in AMQP 1.0 implementation of > session.sync() in C++ client. On AMQP 0-10, the method sends execution.sync > frame to the broker, asking for prompt delivery status to be sent. But 1.0 > client does not invoke any such command. For performance impact, see > QPID-5701 I raised. > > My question is: what would be reasonable way of telling the broker "please > send me all dispositions now" over AMQP 1.0? Any ideas? Checking AMQP 1.0 > spec I dont see a direct way.. > > Kind regards, > Pavel > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
