qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rakesh Kushwaha <kushwah...@gmail.com>
Subject Re: Question on amqp 1.0 payload Type ??
Date Fri, 02 Aug 2013 11:37:52 GMT
Hi Rob,

streaming or large message transfer is enabled by just enabling <more=
true>  in transfer frame .

 for Amqp sequence , amqp specification says* "A sequence section contains
an arbitrary number of structured data elements". *
 as parent type of amqp sequence is LIST  which is a compound data type
will have size encoded for this data type .
streaming can be implemented  transfer frame 's <more=true> if we can't
send whole list elements in one go as I understand.

For DATA type also above holds true as per my understanding .

I can't related your answer through amqp specification here ,

Now for amqp value specfication says "An* amqp-value section contains a
single AMQP value." *
if size of this amqp value is more than then also streaming may be required
. what i don't understand is what this "* single AMQP value" means. (Number
1 confusion)*

*as amqp value parent type *(any type) ,ideally this can include any thing
"primitives types , described typed , compound types". if * is replaced by
list then it can have multiple elements .*

*and if * can replaced by Binary then it can have DATA also.*
*
*

*
*
<type name="data" class="restricted" source="binary" provides="section">*
*
<type name="amqp-sequence" class="restricted" source="list"
provides="section">
<type name="amqp-value" class="restricted" source="*" provides="section">
 // here * can be both list, binary.

** means any type why we need DATA and SEQUENCE (number 2 confusion).*
*:)*
*Regards,*
*Rakesh*



*
*
*Regards,*
*Rakesh*
*
*
*
*
*
*
















On Fri, Aug 2, 2013 at 1:40 PM, Rob Godfrey <rob.j.godfrey@gmail.com> wrote:

> On 2 August 2013 09:35, Rakesh Kushwaha <kushwaha.r@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 .
> >
> >
> As I answered before: data and sequence allow for the case where the size
> of the data is not known up front by the sending application. AmqpValue
> requires that you know the size before sending.
>
> -- Rob
>
>
> > Regards,
> > Rakesh
> >
> >
> > On Thu, Aug 1, 2013 at 6:54 PM, Rob Godfrey <rob.j.godfrey@gmail.com>
> > wrote:
> >
> > > Yes indeed Gordon, thank you for clarifying
> > >
> > > -- Rob
> > >
> > >
> > > On 1 August 2013 15:01, Gordon Sim <gsim@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-unsubscribe@qpid.apache.org>
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message