You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by William Henry <wh...@redhat.com> on 2012/11/14 19:31:02 UTC
Proton-46
I would like to reopen Proton-46. I see the changes made to Messenger but it is unclear how this can be of any value unless you can get at what subscription an incoming message is associated with.
Perhaps all that is needed is an explanation of what was "fixed" when it was closed. Or perhaps there is something missing from Message. (?)
Best,
William
Re: Proton-46
Posted by Rafael Schloming <rh...@alum.mit.edu>.
Yeah, sorry, I was racing to get the 0.2 release out. I figured you'd
rather have it undocumented than not have it at all. ;-)
--Rafael
On Wed, Nov 14, 2012 at 7:57 PM, William Henry <wh...@redhat.com> wrote:
>
>
> ----- Original Message -----
> > On Wed, Nov 14, 2012 at 7:31 PM, William Henry <wh...@redhat.com>
> > wrote:
> >
> > > I would like to reopen Proton-46. I see the changes made to
> > > Messenger but
> > > it is unclear how this can be of any value unless you can get at
> > > what
> > > subscription an incoming message is associated with.
> > >
> > >
> > > Perhaps all that is needed is an explanation of what was "fixed"
> > > when it
> > > was closed. Or perhaps there is something missing from Message. (?)
> > >
> >
> > You can use this[1] to access the subscription for the message last
> > retrieved by pn_messenger_get(...):
> >
> > [1] pn_subscription_t
> > *pn_messenger_incoming_subscription(pn_messenger_t
> > *messenger);
>
>
> Great. Might be useful to add some comment to these new functions at some
> point.
>
> Also a comment on the jira would have cleared this up ;-)
>
> Thanks,
>
> William
>
> >
> > --Rafael
> >
>
Re: Proton-46
Posted by William Henry <wh...@redhat.com>.
----- Original Message -----
> On Wed, Nov 14, 2012 at 7:31 PM, William Henry <wh...@redhat.com>
> wrote:
>
> > I would like to reopen Proton-46. I see the changes made to
> > Messenger but
> > it is unclear how this can be of any value unless you can get at
> > what
> > subscription an incoming message is associated with.
> >
> >
> > Perhaps all that is needed is an explanation of what was "fixed"
> > when it
> > was closed. Or perhaps there is something missing from Message. (?)
> >
>
> You can use this[1] to access the subscription for the message last
> retrieved by pn_messenger_get(...):
>
> [1] pn_subscription_t
> *pn_messenger_incoming_subscription(pn_messenger_t
> *messenger);
Great. Might be useful to add some comment to these new functions at some point.
Also a comment on the jira would have cleared this up ;-)
Thanks,
William
>
> --Rafael
>
Re: Proton-46
Posted by Rafael Schloming <rh...@alum.mit.edu>.
On Wed, Nov 14, 2012 at 7:31 PM, William Henry <wh...@redhat.com> wrote:
> I would like to reopen Proton-46. I see the changes made to Messenger but
> it is unclear how this can be of any value unless you can get at what
> subscription an incoming message is associated with.
>
>
> Perhaps all that is needed is an explanation of what was "fixed" when it
> was closed. Or perhaps there is something missing from Message. (?)
>
You can use this[1] to access the subscription for the message last
retrieved by pn_messenger_get(...):
[1] pn_subscription_t *pn_messenger_incoming_subscription(pn_messenger_t
*messenger);
--Rafael