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). -- Rob On 1 August 2013 13:25, Rakesh Kushwaha <kushwah...@gmail.com> wrote: > Hi , > > As Per amqp 1.0, below types are supported for payload part of amqp . > > 3.2.6 Data > <type name="data" class="restricted" source="binary" provides="section"> > <descriptor name="amqp:data:binary" code="0x00000000:0x00000075"/> > </type> > > > A data section contains opaque binary data. > > > 3.2.7 AMQP Sequence > <type name="amqp-sequence" class="restricted" source="list" > provides="section"> > <descriptor name="amqp:amqp-sequence:list" code="0x00000000:0x00000076"/> > </type> > A sequence section contains an arbitrary number of structured data > elements. > > > 3.2.8 AMQP Value > <type name="amqp-value" class="restricted" source="*" provides="section"> > <descriptor name="amqp:amqp-value:*" code="0x00000000:0x00000077"/> > </type> > An amqp-value section contains a single AMQP value. > > > > for <AMQP Value> , what is meaning of 'source = *' here , if it means any > type of primitive or compound structure then why we needed first two types > <DATA> and <AMQP Sequeuence>. > > > Regards, > Rakesh >
