+1
[X] Ship it! (Release 0.2 RC3 as 0.2)
On Sun, Nov 4, 2012 at 7:09 PM, Rafael Schloming wrote:
> Hi, I did a bit more testing over the weekend and posted an RC3 here:
>
> http://people.apache.org/~rhs/qpid-proton-0.2rc3
>
> The only changes are fixing a minor bug in the ack stuff and adding t
Hiram Chirino created PROTON-115:
Summary: Expose API to access link name.
Key: PROTON-115
URL: https://issues.apache.org/jira/browse/PROTON-115
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490561#comment-13490561
]
Rob Godfrey commented on PROTON-115:
Added getName() to Link in proton-j
[
https://issues.apache.org/jira/browse/PROTON-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated PROTON-115:
---
Fix Version/s: 0.3
> Expose API to access link name.
> ---
>
>
-1
Sadly I have to vote against myself due to a bug I just found. Will follow
up with RC4 presently.
--Rafael
On Sun, Nov 4, 2012 at 7:09 PM, Rafael Schloming wrote:
> Hi, I did a bit more testing over the weekend and posted an RC3 here:
>
> http://people.apache.org/~rhs/qpid-proton-0.2rc3
>
>
Posted here: http://people.apache.org/~rhs/qpid-proton-0.2rc4/
[ ] Ship it! (Release RC4 as 0.2)
[ ] No (We need another RC because...)
The only difference between RC3 and RC4 for proton-c is a one line change
in engine.c that ensures that pn_transport_output will not fail to produce
output under
[X] Ship it! (Release RC4 as 0.2)
Tested java and reviewed C change.
-- Rob
On 5 November 2012 13:19, Rafael Schloming wrote:
> Posted here: http://people.apache.org/~rhs/qpid-proton-0.2rc4/
>
> [ ] Ship it! (Release RC4 as 0.2)
> [ ] No (We need another RC because...)
>
> The only difference
On Mon, Nov 05, 2012 at 07:19:30AM -0500, Rafael Schloming wrote:
> Posted here: http://people.apache.org/~rhs/qpid-proton-0.2rc4/
>
> [X] Ship it! (Release RC4 as 0.2)
> [ ] No (We need another RC because...)
>
> The only difference between RC3 and RC4 for proton-c is a one line change
> in engi
[x] Ship it. Reviewed the C code change with Rafi.
Rajith
On Mon, Nov 5, 2012 at 7:29 AM, Rob Godfrey wrote:
> [X] Ship it! (Release RC4 as 0.2)
>
> Tested java and reviewed C change.
>
> -- Rob
>
> On 5 November 2012 13:19, Rafael Schloming wrote:
>
>> Posted here: http://people.apache.org/~rh
On Mon, Nov 5, 2012 at 3:54 PM, Darryl L. Pierce wrote
>
> Will the final, official URL for the source be:
>
> http://www.apache.org/dist/proton/$VER/qpid-proton-c-$VER.tar.gz
>
> ? I'd like to clean up another rpmlint error where it doesn't like a
> non-URI value for the source.
Yes, with the c
Ted Ross created PROTON-116:
---
Summary: Proton sends explicit disposition for pre-settled messages
Key: PROTON-116
URL: https://issues.apache.org/jira/browse/PROTON-116
Project: Qpid Proton
Issue Ty
Ted mentioned that with 0.2 came a change in settlement behavior.
Deliveries are now pre-settled.
As a matter of default api behavior, what's the rationale for pre-settling
rather than auto settling deliveries? I have no particular preference;
I'm aiming to understand the principle involved.
[
https://issues.apache.org/jira/browse/PROTON-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490737#comment-13490737
]
Rafael H. Schloming commented on PROTON-116:
It's not illegal to send the spur
Surely its going to be in /dist/qpid/proton since its a sub project?
Robbie
On 5 November 2012 16:11, Rafael Schloming wrote:
> On Mon, Nov 5, 2012 at 3:54 PM, Darryl L. Pierce
> wrote
> >
> > Will the final, official URL for the source be:
> >
> > http://www.apache.org/dist/proton/$VER/qpid-p
Hiram Chirino created PROTON-117:
Summary: Consider replacing org.apache.qpid.proton.engine.Sequence
with java.util.Iterator
Key: PROTON-117
URL: https://issues.apache.org/jira/browse/PROTON-117
Proje
Gordon Sim created PROTON-118:
-
Summary: Add support for Messenger API
Key: PROTON-118
URL: https://issues.apache.org/jira/browse/PROTON-118
Project: Qpid Proton
Issue Type: New Feature
Gordon Sim created PROTON-119:
-
Summary: Engine can switch from SASL to plain AMQP transport too
soon
Key: PROTON-119
URL: https://issues.apache.org/jira/browse/PROTON-119
Project: Qpid Proton
I
Gordon Sim created PROTON-120:
-
Summary: Link.delivery() signature takes offset and size which are
not used
Key: PROTON-120
URL: https://issues.apache.org/jira/browse/PROTON-120
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-120:
--
Attachment: delivery_signature.patch
This patch changes the signature, removing the offset and size. Th
[
https://issues.apache.org/jira/browse/PROTON-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-119:
--
Attachment: sasl_engine.patch
One possible fix... this simply adds a flag to track whether the init has
[
https://issues.apache.org/jira/browse/PROTON-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned PROTON-118:
-
Assignee: Gordon Sim
> Add support for Messenger API
> -
>
>
[
https://issues.apache.org/jira/browse/PROTON-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned PROTON-119:
-
Assignee: Gordon Sim
> Engine can switch from SASL to plain AMQP transport too soon
> ---
[
https://issues.apache.org/jira/browse/PROTON-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-118:
--
Attachment: engine.patch
driver.patch
This is just an early preview of my initial stab
[
https://issues.apache.org/jira/browse/PROTON-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved PROTON-119.
---
Resolution: Fixed
> Engine can switch from SASL to plain AMQP transport too soon
> --
[
https://issues.apache.org/jira/browse/PROTON-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490881#comment-13490881
]
Gordon Sim commented on PROTON-118:
---
Two deviations from the C to highlight:
(i) at pre
[
https://issues.apache.org/jira/browse/PROTON-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned PROTON-120:
-
Assignee: Gordon Sim
> Link.delivery() signature takes offset and size which are not used
> -
[
https://issues.apache.org/jira/browse/PROTON-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490910#comment-13490910
]
Ken Giusti commented on PROTON-60:
--
Just for reference:
This commit:
http://svn.apache.o
Andrew Stitcher created PROTON-121:
--
Summary: Platform specific code is mixed in with platform
independent code
Key: PROTON-121
URL: https://issues.apache.org/jira/browse/PROTON-121
Project: Qpid Pro
On Mon, Nov 5, 2012 at 6:08 PM, Robbie Gemmell wrote:
> Surely its going to be in /dist/qpid/proton since its a sub project?
>
Oops, I misread the post. It will be exactly where 0.1 is except it will
say 0.2 instead:
http://www.apache.org/dist/qpid/proton/0.1/qpid-proton-c-0.1.tar.gz
--Rafael
On Mon, Nov 05, 2012 at 10:37:34PM +0100, Rafael Schloming wrote:
> On Mon, Nov 5, 2012 at 6:08 PM, Robbie Gemmell
> wrote:
>
> > Surely its going to be in /dist/qpid/proton since its a sub project?
> >
>
> Oops, I misread the post. It will be exactly where 0.1 is except it will
> say 0.2 instea
On Mon, Nov 5, 2012 at 5:57 PM, Justin Ross wrote:
> Ted mentioned that with 0.2 came a change in settlement behavior.
> Deliveries are now pre-settled.
>
> As a matter of default api behavior, what's the rationale for pre-settling
> rather than auto settling deliveries? I have no particular pre
31 matches
Mail list logo
