My Question was on format , if for amqp value we have <source=*> that means it can have both BINARY and LIST kind of data type or any kind permissible amqp data type .
then why we needed DATA and AMQP SEQUENCE . Regards, Rakesh On Fri, Aug 2, 2013 at 1:05 PM, Rakesh Kushwaha <kushwah...@gmail.com>wrote: > My Question was on format , if for amqp value we have <source=*> that > means it can have both BINARY and LIST kind data type . > > then why we needed DATA and AMQP SEQUENCE . > > Regards, > Rakesh > > > On Thu, Aug 1, 2013 at 6:54 PM, Rob Godfrey <rob.j.godf...@gmail.com>wrote: > >> Yes indeed Gordon, thank you for clarifying >> >> -- Rob >> >> >> On 1 August 2013 15:01, Gordon Sim <g...@redhat.com> wrote: >> >> > On 08/01/2013 01:52 PM, Rob Godfrey wrote: >> > >> >> Data and AmqpSequence allow the sender to start sending data without >> >> knowing how many bytes / values the data is going to consist of. This >> >> allows for streaming scenarios where the size of the data is not known >> up >> >> front. >> >> >> >> Note also that there is no bound to the size of Data or AmqpSequence, >> >> whereas an AmqpValue will always be bounded by the largest AMQP data >> type >> >> - >> >> i.e. 4Gb (not that I would ever recommend sending a single message of >> >> greater than 4Gb). >> >> >> > >> > Just to clarify, each individual section of type Data or AmqpSequence is >> > bounded and has its size encoded upfront. The ability to stream and/or >> send >> > unbounded amounts of data comes through sending multiple such sections >> in >> > the same message. Right? (Whereas only a single AmqpValue section is >> > allowed per message). >> > >> > >> > >> ------------------------------**------------------------------**--------- >> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.**org< >> users-unsubscr...@qpid.apache.org> >> > For additional commands, e-mail: users-h...@qpid.apache.org >> > >> > >> > >
