[jira] [Updated] (PROTON-261) pn_delivery_local_state and pn_delivery_remote_state can return a zero value (outside that defined by the pn_disposition_t enum)

[ https://issues.apache.org/jira/browse/PROTON-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-261: -- Description: In proton-c, pn_delivery_local_state and pn_delivery_remote_state are defined as returnin

[jira] [Commented] (PROTON-261) pn_delivery_local_state and pn_delivery_remote_state can return a zero value (outside that defined by the pn_disposition_t enum)

[ https://issues.apache.org/jira/browse/PROTON-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595724#comment-13595724 ] Keith Wall commented on PROTON-261: --- I like the idea to extend the pn_disposition_t enum

Re: Fwd: put vs. send

On 3/6/13 3:45 AM, Rafael Schloming wrote: Oops, meant to send this to the list. -- Forwarded message -- From: Rafael Schloming Date: Tue, Mar 5, 2013 at 6:44 PM Subject: Re: put vs. send To: Bozo Dragojevic On Tue, Mar 5, 2013 at 3:25 PM, Bozo Dragojevic wrote: Wow, by not

[jira] [Closed] (PROTON-266) JNIMessage does not encode message body

[ https://issues.apache.org/jira/browse/PROTON-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed PROTON-266. - > JNIMessage does not encode message body > --- > > K

[jira] [Resolved] (PROTON-266) JNIMessage does not encode message body

[ https://issues.apache.org/jira/browse/PROTON-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved PROTON-266. --- Resolution: Fixed Fix by rev 1453850 > JNIMessage does not encode message body > ---

[jira] [Resolved] (PROTON-264) Proton-J and Proton-C transports make inconsistent use of return values within methods input and output

[ https://issues.apache.org/jira/browse/PROTON-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved PROTON-264. --- Resolution: Fixed Change committed at rev. 1453849 > Proton-J and Proton-C transport

[jira] [Closed] (PROTON-264) Proton-J and Proton-C transports make inconsistent use of return values within methods input and output

[ https://issues.apache.org/jira/browse/PROTON-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed PROTON-264. - > Proton-J and Proton-C transports make inconsistent use of return values > within methods input and out

[jira] [Commented] (PROTON-256) Improve Engine API JavaDoc

[ https://issues.apache.org/jira/browse/PROTON-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595910#comment-13595910 ] Keith Wall commented on PROTON-256: --- Change committed at rev 1453851. Leaving Jira open

[jira] [Resolved] (PROTON-257) Add example to illustrate use of proton-j API

[ https://issues.apache.org/jira/browse/PROTON-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved PROTON-257. --- Resolution: Fixed Change committed at rev. 1453852 > Add example to illustrate use o

[jira] [Updated] (PROTON-257) Add example to illustrate use of proton-j API

[ https://issues.apache.org/jira/browse/PROTON-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-257: -- Fix Version/s: 0.5 > Add example to illustrate use of proton-j API > --

[jira] [Resolved] (PROTON-263) JNIDelivery.isPartial should delegate to pn_delivery_partial

[ https://issues.apache.org/jira/browse/PROTON-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved PROTON-263. --- Resolution: Fixed Change committed by rev. 1453848 > JNIDelivery.isPartial should de

[jira] [Closed] (PROTON-263) JNIDelivery.isPartial should delegate to pn_delivery_partial

[ https://issues.apache.org/jira/browse/PROTON-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed PROTON-263. - > JNIDelivery.isPartial should delegate to pn_delivery_partial >

Re: Proton Messenger and the Request/Response pattern

Hi All, I wanted to re-raise Ted's suggestion regarding the need for a better Messenger API for handling reply-to's. I've could've used this recently while designing a "echo" stress test for Messenger. For my client, I have two requirements: 1) I don't want to have to assign a publicly visibl

[jira] [Commented] (PROTON-110) java.lang.NullPointerException: the handle field is mandatory

[ https://issues.apache.org/jira/browse/PROTON-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595930#comment-13595930 ] Keith Wall commented on PROTON-110: --- Hiram Can you describe the method you used to caus

Re: Proton Messenger and the Request/Response pattern

- Original Message - > Hi All, > > I wanted to re-raise Ted's suggestion regarding the need for a better > Messenger API for handling reply-to's. > > I've could've used this recently while designing a "echo" stress test > for Messenger. For my client, I have two requirements: > > 1) I

Re: Proton Messenger and the Request/Response pattern

- Original Message - > From: "Michael Goulish" > To: proton@qpid.apache.org > Sent: Thursday, March 7, 2013 9:48:24 AM > Subject: Re: Proton Messenger and the Request/Response pattern > > > > - Original Message - > > Hi All, > > > > I wanted to re-raise Ted's suggestion regar

[jira] [Created] (PROTON-267) Driver ignores socket close event code returned from socket read/write

Ken Giusti created PROTON-267: - Summary: Driver ignores socket close event code returned from socket read/write Key: PROTON-267 URL: https://issues.apache.org/jira/browse/PROTON-267 Project: Qpid Proton

[jira] [Assigned] (PROTON-267) Driver ignores socket close event code returned from socket read/write

[ https://issues.apache.org/jira/browse/PROTON-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-267: - Assignee: Ken Giusti > Driver ignores socket close event code returned from socket read/write

Re: Proton Messenger and the Request/Response pattern

- Original Message - > > > - Original Message - > > From: "Michael Goulish" > > To: proton@qpid.apache.org > > Sent: Thursday, March 7, 2013 9:48:24 AM > > Subject: Re: Proton Messenger and the Request/Response pattern > > > > > > > > - Original Message - > > > Hi Al

[jira] [Assigned] (PROTON-259) proton-j engine operations do not check if the endpoint is already closed

[ https://issues.apache.org/jira/browse/PROTON-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey reassigned PROTON-259: Assignee: Philip Harvey > proton-j engine operations do not check if the endpoint is al

[jira] [Commented] (PROTON-267) Driver ignores socket close event code returned from socket read/write

[ https://issues.apache.org/jira/browse/PROTON-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595986#comment-13595986 ] Ken Giusti commented on PROTON-267: --- Reviewboard https://reviews.apache.org/r/9802/

can't commit

I'm trying to commit my docs dir to the repo, and seeing this: svn commit docs svn: E175013: Commit failed (details follow): svn: E175013: Access to '/repos/asf/!svn/me' forbidden Do I need more permissions for this ?

Re: can't commit

There aren't any repo level access controls, so if you have qpid commit bits you should be able to commit to proton. Is it possible you checked out via an "http" repo URL rather than an "https" repo URL? If so then your checkout is going to be read-only and you'll have to use "svn switch" to change

Re: can't commit

Gah! Thanks. "Committers can check out the code using HTTPS:" Note to Self: RTFM - Original Message - There aren't any repo level access controls, so if you have qpid commit bits you should be able to commit to proton. Is it possible you checked out via an "http" repo URL rather than

docs dir landed

"docs" dir is there at last, with one whole doc in it. send_and_receive.markdown I've tried to capture the stuff we all talked about recently -- looking forward to reviews. Phil - thanks for the markdown idea -- it's extremely cool.

linux quickstart

There's a lot of overlap between this document and the build instructions in the README, but I thought it would be nice to have a one-stop-doc that takes you from nothing to seeing your first example run in 90 seconds. intrunk/docs/quick_start_linux.markdown

to see rendered markdown...

If you would like to see what the rendered documents will look like, go here: http://daringfireball.net/projects/markdown/dingus paste one of the docs in the window, and hit the 'convert' button.

Re: Discrepancy between Java and C "is settled" methods

On Wed, Mar 6, 2013 at 10:27 PM, Phil Harvey wrote: > Ok, I hadn't realised that settling a delivery in proton-c had such a > significant effect on its state. > > Does this imply that it's illegal for an application to use a delivery in > any way once it's called pn_delivery_settle? If so, we shou

Re: put vs. send -- new doc

I like this. I don't think this is the same thing as high level conceptual intro, but may well be more useful right now, and it will always be very useful as recipe book style documentation. I think this is actually quite helpful for the ongoing API discussions. One of the tricky things about deve

Re: put vs. send -- new doc

- Original Message - > I like this. Good! I'm trying to get at the intention, as I understood it from online discussions, and make a doc that makes the intention easy to see. > I don't think this is the same thing as high level > conceptual > intro, but may well be more useful ri

Re: put vs. send -- new doc

On Thu, Mar 7, 2013 at 3:18 PM, Michael Goulish wrote: > > > > I think this is actually quite helpful for the ongoing API > > discussions. One > > of the tricky things about developing a simple API is that everyone > > has > > their own scenario that they want to be simple, and sometimes making >