Re: delivery.setPayload

2014-05-14 Thread Rafael Schloming
On Wed, May 14, 2014 at 1:05 PM, Clebert Suconic wrote: > I was just playing with possibilities and trying to find ways to improve > the API how things are done. > > > > > The interface is designed to > > operate in terms of chunks of message data rather than in terms of an > > entire message. >

Re: delivery.setPayload

2014-05-14 Thread Clebert Suconic
I was just playing with possibilities and trying to find ways to improve the API how things are done. > The interface is designed to > operate in terms of chunks of message data rather than in terms of an > entire message. That's one thing that I'm lacking control through the API actually.

Re: delivery.setPayload

2014-05-14 Thread Rafael Schloming
On Tue, May 13, 2014 at 4:40 PM, Clebert Suconic wrote: > > > On May 13, 2014, at 1:46 PM, Rafael Schloming wrote: > > > I'm not sure this will work as an API. One problem I see with this is > that > > it is circumventing the engine's flow control logic. If you notice there > is > > logic inside

Client APIs and AMQP 1.0 (was Re: Using the messenger API to connect to a server without sending or subscribing)

2014-05-14 Thread Gordon Sim
On 04/28/2014 10:21 PM, Gordon Sim wrote: On 04/23/2014 05:17 PM, Fraser Adams wrote: BTW I wouldn't want to come across as favouring proton Messenger or qpid::messaging over the other, as I said previously they are peer APIs with different advantages and disadvantages, I'd certainly agree the

[jira] [Resolved] (PROTON-579) Typo in proton.php use of $self should be $this

2014-05-14 Thread Rafael H. Schloming (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-579. Resolution: Fixed > Typo in proton.php use of $self should be $this > -