[
https://issues.apache.org/jira/browse/PROTON-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-960.
Resolution: Fixed
Fix Version/s: 0.10
> On error Proton can send an open and a cl
[
https://issues.apache.org/jira/browse/PROTON-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-959.
Resolution: Fixed
Fix Version/s: 0.10
> On error Proton can send an open and a cl
[
https://issues.apache.org/jira/browse/PROTON-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-963.
Resolution: Fixed
> [SASL] Raise PN_TRANSPORT_ERROR events with correct condition
[
https://issues.apache.org/jira/browse/PROTON-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644471#comment-14644471
]
Andrew Stitcher commented on PROTON-923:
This is the issue for raising
Andrew Stitcher created PROTON-963:
--
Summary: [SASL] Raise PN_TRANSPORT_ERROR events with correct
condition for authentication failure
Key: PROTON-963
URL: https://issues.apache.org/jira/browse/PROTON-963
[
https://issues.apache.org/jira/browse/PROTON-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643485#comment-14643485
]
Andrew Stitcher commented on PROTON-923:
I can't reproduce this bug
[
https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642833#comment-14642833
]
Andrew Stitcher commented on PROTON-961:
Is there a test for large messages?
Andrew Stitcher created PROTON-960:
--
Summary: On error Proton can send an open and a close frame during
the SASL negotiation (before sending the AMQP header)
Key: PROTON-960
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/PROTON-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-959:
---
Description:
In the following trace of some transport tests you will see that many of the
Andrew Stitcher created PROTON-959:
--
Summary: On error Proton can send an open and a close frame before
sending the AMQP header
Key: PROTON-959
URL: https://issues.apache.org/jira/browse/PROTON-959
[
https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-951:
---
Description:
When building proton-C using a python 3.4 virtualenv make install fails
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633992#comment-14633992
]
Andrew Stitcher edited comment on PROTON-952 at 7/21/15 4:3
[
https://issues.apache.org/jira/browse/PROTON-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-953:
---
Description:
In the current Travis CI build the tox tests fail to correctly build the python
[
https://issues.apache.org/jira/browse/PROTON-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-953:
---
Assignee: Ken Giusti
> Travis CI tox tests fail to correctly build python 2.6 extension
Andrew Stitcher created PROTON-953:
--
Summary: Travis CI tox tests fail to correctly build python 2.6
extension lib
Key: PROTON-953
URL: https://issues.apache.org/jira/browse/PROTON-953
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-952:
---
Assignee: Ken Giusti
> Building Proton with python 2.6 and python 3.4 on Travis CI finds
[
https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-951:
---
Assignee: Ken Giusti
> Make install fails when building Proton-C with python
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633992#comment-14633992
]
Andrew Stitcher commented on PROTON-952:
Build log for python 3.4 (2.6 is sim
[
https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633983#comment-14633983
]
Andrew Stitcher commented on PROTON-951:
This may not have been noticed be
Andrew Stitcher created PROTON-952:
--
Summary: Building Proton with python 2.6 and python 3.4 on Travis
CI finds and links wrong libpython
Key: PROTON-952
URL: https://issues.apache.org/jira/browse/PROTON-952
[
https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-951:
---
Attachment: py34fail
Attached Output from "make install"
> Make install fails
Andrew Stitcher created PROTON-951:
--
Summary: Make install fails when building Proton-C with python 3.4
Key: PROTON-951
URL: https://issues.apache.org/jira/browse/PROTON-951
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622503#comment-14622503
]
Andrew Stitcher commented on PROTON-941:
Agreed.
Incidentally The python bin
[
https://issues.apache.org/jira/browse/PROTON-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622493#comment-14622493
]
Andrew Stitcher commented on PROTON-941:
I think that starts next
On Mon, 2015-07-06 at 11:28 -0700, Rafael Schloming wrote:
> +1
>
> The only issue that has me worried here is the sasl interop story between
> proton-c and proton-j. I can cut a release later today just to give us
> something to poke at, but there may still be sasl work needed.
I have a blocking
[
https://issues.apache.org/jira/browse/PROTON-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615620#comment-14615620
]
Andrew Stitcher commented on PROTON-201:
[~cliffjansen], I believe thi
[
https://issues.apache.org/jira/browse/PROTON-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-201:
---
Assignee: Cliff Jansen (was: Andrew Stitcher)
> Provide a C++ Messenger and Message cl
Andrew Stitcher created PROTON-934:
--
Summary: Build tests fail if Java is not available
Key: PROTON-934
URL: https://issues.apache.org/jira/browse/PROTON-934
Project: Qpid Proton
Issue Type
[
https://issues.apache.org/jira/browse/PROTON-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-933.
Resolution: Fixed
Fix Version/s: 0.10
> Cyrus SASL GSSAPI plugin can error if s
Andrew Stitcher created PROTON-933:
--
Summary: Cyrus SASL GSSAPI plugin can error if sent long buffers.
Key: PROTON-933
URL: https://issues.apache.org/jira/browse/PROTON-933
Project: Qpid Proton
On Mon, 2015-07-06 at 13:14 -0400, Andrew Stitcher wrote:
> On Mon, 2015-07-06 at 17:48 +0100, Robbie Gemmell wrote:
> > ...
> > The old toggle only used to define whether sasl was required or not
> > (which it historically was once you enabled the sasl layer, and the
On Mon, 2015-07-06 at 17:48 +0100, Robbie Gemmell wrote:
> ...
> The old toggle only used to define whether sasl was required or not
> (which it historically was once you enabled the sasl layer, and the
> toggle was never implemented in proton-j), whereas IIRC the new
> 'requireAuth' governs that b
On Mon, 2015-07-06 at 11:30 -0400, Rafael Schloming wrote:
> I wired in allowSkip in a very minimal way just to restore the ability to
> force the old behaviour. It would be a fairly trivial to change the name of
> course,
I'm not sure if that really applies as the method is on a different
object
On Mon, 2015-07-06 at 10:56 -0400, Rafael Schloming wrote:
> On Mon, Jul 6, 2015 at 9:52 AM, Robbie Gemmell
> wrote:
>
> > Is this change allowing clients to skip the SASL layer when connecting
> > to servers that have enabled the SASL layer? If so, how is the new
> > default behaviour disabled?
[
https://issues.apache.org/jira/browse/PROTON-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-911.
Resolution: Implemented
Fix Version/s: 0.10
Except for bug fixing, this is now
[
https://issues.apache.org/jira/browse/PROTON-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-929.
Resolution: Fixed
> [SASL] If both client and server specify ANONYMOUS mech connect
Andrew Stitcher created PROTON-918:
--
Summary: Jython interop tests failing since e38957ae5115
Key: PROTON-918
URL: https://issues.apache.org/jira/browse/PROTON-918
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591729#comment-14591729
]
Andrew Stitcher commented on PROTON-915:
The current implementation will
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-915.
Resolution: Fixed
> Incompatible protocol header handled incorrec
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590772#comment-14590772
]
Andrew Stitcher commented on PROTON-915:
I've now committed the pa
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590579#comment-14590579
]
Andrew Stitcher commented on PROTON-915:
[~gemmellr] I think this w
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-915:
---
Assignee: Rafael H. Schloming (was: Andrew Stitcher)
> Incompatible protocol header hand
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590432#comment-14590432
]
Andrew Stitcher commented on PROTON-915:
Assigned to [~rhs] for comment on
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-915:
---
Attachment: 0001-PROTON-915-Send-correct-AMQP-header-upon-protocol-mi.patch
Putative fix for
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590430#comment-14590430
]
Andrew Stitcher commented on PROTON-915:
I have a fix for this now - try
[
https://issues.apache.org/jira/browse/PROTON-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590056#comment-14590056
]
Andrew Stitcher commented on PROTON-915:
A reproducer script would be
Andrew Stitcher created PROTON-911:
--
Summary: Implement SASL security layer
Key: PROTON-911
URL: https://issues.apache.org/jira/browse/PROTON-911
Project: Qpid Proton
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/PROTON-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reassigned PROTON-911:
--
Assignee: Andrew Stitcher
> Implement SASL security la
Andrew Stitcher created PROTON-910:
--
Summary: Proton-J SASL implementation should support new SASL APIs
Key: PROTON-910
URL: https://issues.apache.org/jira/browse/PROTON-910
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582485#comment-14582485
]
Andrew Stitcher commented on PROTON-909:
There are now tests that exercise ne
[
https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-867.
Resolution: Fixed
Fix Version/s: 0.10
This issue has been resolved with the changes
[
https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582476#comment-14582476
]
Andrew Stitcher edited comment on PROTON-867 at 6/11/15 8:2
[
https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582476#comment-14582476
]
Andrew Stitcher commented on PROTON-867:
It would be helpful to the user if t
[
https://issues.apache.org/jira/browse/PROTON-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-866.
Resolution: Fixed
Fix Version/s: 0.10
> Implement SASL external with TLS cli
[
https://issues.apache.org/jira/browse/PROTON-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reassigned PROTON-909:
--
Assignee: Andrew Stitcher
> Tests for new SASL features and mechani
Andrew Stitcher created PROTON-909:
--
Summary: Tests for new SASL features and mechanisms
Key: PROTON-909
URL: https://issues.apache.org/jira/browse/PROTON-909
Project: Qpid Proton
Issue
On Wed, 2015-06-03 at 16:57 +0100, Gordon Sim wrote:
> On 06/03/2015 04:14 PM, logty wrote:
> > I ran with PN_TRACE_FRM=1, and it returned the following log results. The
> > connection has been working with Python but not with C. It seems to be some
> > SASL issue, any thoughts?
>
> The c client i
[
https://issues.apache.org/jira/browse/PROTON-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569559#comment-14569559
]
Andrew Stitcher commented on PROTON-344:
Note that all these commits are actu
Andrew Stitcher created PROTON-887:
--
Summary: Windows SSL implementation needs working version of
pn_ssl_get_remote_subject()
Key: PROTON-887
URL: https://issues.apache.org/jira/browse/PROTON-887
[
https://issues.apache.org/jira/browse/PROTON-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542750#comment-14542750
]
Andrew Stitcher commented on PROTON-885:
I agree wth [~dnwe] that it looks
[
https://issues.apache.org/jira/browse/PROTON-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542256#comment-14542256
]
Andrew Stitcher commented on PROTON-885:
[~flaper87] Just eyeballing the patc
[
https://issues.apache.org/jira/browse/PROTON-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-562:
---
Fix Version/s: (was: 0.10)
0.9
> More gracefully handle connections
[
https://issues.apache.org/jira/browse/PROTON-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-562.
Resolution: Fixed
The misleading error messages are no longer present, and the underlying
[
https://issues.apache.org/jira/browse/PROTON-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-562:
---
Fix Version/s: 0.10
> More gracefully handle connections to non-1.0 part
[
https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-877.
Resolution: Fixed
> proton-c sasl client hangs on server pipel
Since Rafi pushed 223bbc8bd50a34282ef02952392fd4321113f770 my Linux
(Fedora 21) builds have been failing [1]. I've finally tracked it down
to some problem with ccache-swig.
So if you have ccache installed (which is generally a good idea as it
speeds up builds a lot) you need to avoid the ccache ve
On Wed, 2015-05-06 at 14:03 -0400, Rafael Schloming wrote:
> We seem to have reached consensus here, but I haven't seen any commits on
> this. We should probably fix this before 0.10 so we don't end up putting
> out a new API and then deprecating it in the next release. Is anyone
> actually working
On Thu, 2015-05-07 at 11:09 -0400, Andrew Stitcher wrote:
> On Wed, 2015-05-06 at 23:42 +0100, Gordon Sim wrote:
> > ...
> > Apparently these are posix functions and are not included in c99. Using
> > the proton equivalents in util.h works. Let me know if you want me to
>
On Wed, 2015-05-06 at 23:42 +0100, Gordon Sim wrote:
> ...
> Apparently these are posix functions and are not included in c99. Using
> the proton equivalents in util.h works. Let me know if you want me to
> commit that.
Gah, sorry I should have spotted that myself earlier.
I will fix it - I thi
[
https://issues.apache.org/jira/browse/PROTON-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-879.
Resolution: Fixed
> null initial response makes cyrus challenge when it probably should
On Wed, 2015-05-06 at 22:22 +0100, Gordon Sim wrote:
> > [ 70%] Building C object
> > proton-c/bindings/javascript/CMakeFiles/qpid-proton-bitcode.dir/__/__/src/sasl/sasl.c.o
> > /home/gordon/projects/proton-git/proton-c/src/sasl/sasl.c:224:9: error:
> > implicit declaration of function 'strncasec
[
https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-867:
---
Description: Currently PLAIN is never offered by Proton acting as a server
because the SASL
[
https://issues.apache.org/jira/browse/PROTON-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-868.
Resolution: Fixed
Fix Version/s: 0.10
> Make Pipelined ANONYMOUS authentication w
[
https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526709#comment-14526709
]
Andrew Stitcher commented on PROTON-877:
[~rhs] could you give some more con
[
https://issues.apache.org/jira/browse/PROTON-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523247#comment-14523247
]
Andrew Stitcher commented on PROTON-875:
This is the symptom of fall
[
https://issues.apache.org/jira/browse/PROTON-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher closed PROTON-875.
--
Resolution: Duplicate
> Proton-C SASL changes break windows self te
[
https://issues.apache.org/jira/browse/PROTON-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reassigned PROTON-875:
--
Assignee: Andrew Stitcher
> Proton-C SASL changes break windows self te
Andrew Stitcher created PROTON-868:
--
Summary: Make Pipelined ANONYMOUS authentication work with
fallback SASL implementation
Key: PROTON-868
URL: https://issues.apache.org/jira/browse/PROTON-868
[
https://issues.apache.org/jira/browse/PROTON-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511873#comment-14511873
]
Andrew Stitcher commented on PROTON-866:
Amongst other things this will req
[
https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reassigned PROTON-867:
--
Assignee: Andrew Stitcher
> Enable PLAIN SASL mech iff connection is encryp
Andrew Stitcher created PROTON-867:
--
Summary: Enable PLAIN SASL mech iff connection is encrypted
Key: PROTON-867
URL: https://issues.apache.org/jira/browse/PROTON-867
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reassigned PROTON-866:
--
Assignee: Andrew Stitcher
> Implement SASL external with TLS client authenticat
Andrew Stitcher created PROTON-866:
--
Summary: Implement SASL external with TLS client authentication
Key: PROTON-866
URL: https://issues.apache.org/jira/browse/PROTON-866
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-862:
---
Description:
The Cyrus SASL library is not 100% suitable for use in other libraries because
Andrew Stitcher created PROTON-862:
--
Summary: Proton using Cyrus SASL library is problematic because
the library has global state
Key: PROTON-862
URL: https://issues.apache.org/jira/browse/PROTON-862
[
https://issues.apache.org/jira/browse/PROTON-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-859.
Resolution: Fixed
Fix Version/s: 0.10
> cyrus sasl not compatible with pre 2.1
On Tue, 2015-04-21 at 14:56 +0100, Robbie Gemmell wrote:
> On 21 April 2015 at 14:48, Robbie Gemmell wrote:
> > On 21 April 2015 at 12:52, Rafael Schloming wrote:
> >> I'm seeing a couple of issues with the recently landed sasl changes. I'm
> >> getting four test failures in the python tests (see
I've received no further feedback at all about this review request.
Do people want me to create a reviewboard item instead?
For reference, this proposed change incorporates all the discussion -
although I haven't necessarily agreed with everyone else's points!
For clarity the main issue that I h
On Wed, 2015-04-15 at 07:13 -0400, Rafael Schloming wrote:
> On Tue, Apr 14, 2015 at 1:27 PM, Alan Conway wrote:
>
> > That works for me, now how do we manage the transition? I don't think we
> > can afford to inflict "yum update proton; all proton apps crash" on our
> > users. That means we cann
[
https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486890#comment-14486890
]
Andrew Stitcher commented on PROTON-334:
Link to the work on github:
h
[
https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-334:
---
Summary: SASL Implementation for Proton C (was: SASL Plug-in for Proton)
> S
On Wed, 2015-04-08 at 10:48 -0400, Alan Conway wrote:
> ...
> The issue is that we need buffer growth AND control over allocation.
> pn_buffer_t forces use of malloc/free/realloc. That won't help if you're
> trying to get the data into a buffer allocated by Go for example. I
> agree a growable buff
On Tue, 2015-04-07 at 09:38 -0400, Alan Conway wrote:
> On Tue, 2015-03-31 at 19:17 +0200, Božo Dragojevič wrote:
> > Given the memory overhead of a pn_data_t before encoding, why not have it
> > own an encode buffer? it could get by with exactly that grow_buffer()
> > callback if ownership is the
On Mon, 2015-03-02 at 20:00 +, Gordon Sim wrote:
> On 03/02/2015 07:07 PM, Rafael Schloming wrote:
> > Hi Everyone,
> >
> > I'd like to propose spinning the first beta (or possibly just RC) for 0.9
> > sometime next week. We've been using alphas to get some early eyes on some
> > of the new API
On Thu, 2015-02-26 at 15:09 -0500, Rafael Schloming wrote:
> ...
> It sounds like one way or another we need at least some design changes. I
> don't think it's workable to have overlapping/close but distinct semantics
> for the API on different platforms (e.g. you can move sockets on one
> platform
On Thu, 2015-02-26 at 13:43 -0500, Alan Conway wrote:
> On Thu, 2015-02-26 at 09:39 +, Dominic Evans wrote:
> > Hi Alan,
> >
> > -Alan Conway wrote: -
> > > I plan to start working on a "go" binding for proton. I
> > > envisage a SWIG binding similar to the other swig-based bindings
On Thu, 2015-02-26 at 12:28 +, Robbie Gemmell wrote:
> ...
> I'm going to post my comments here and on the wiki, as I dont think
> many (except maybe you) will actually see them on the wiki ;)
Thank you for the excellent feedback. I'm going to answer on the wiki -
as it'll save me from cutting
On Tue, 2015-02-24 at 15:48 -0500, Andrew Stitcher wrote:
> ...
> If you are at all interested please go and look at the proposal and
> comment on it there.
Thank you very much to Alan and Jakub for commenting on my proposal.
The reason I asked people to comment over on the wiki is t
On Wed, 2015-02-25 at 10:27 +0100, Jakub Scholz wrote:
> ...
> But I find this part a bit dangerous:
> "Classically in protocols where SASL was not optional the way to avoid
> double authentication was to use the EXTERNAL SASL mechanism. With AMQP,
> SASL is optional, so if SSL is used for client a
On Wed, 2015-02-25 at 10:46 -0500, Alan Conway wrote:
> ...
> One ignorant question: Qpid has a min/max "Security Strength Factor" for
> encryption rather than a binary enable/disable. Is that relevant here?
(Hardly an ignorant question!) You make a very good point, and this
design may indeed be a
201 - 300 of 555 matches
Mail list logo
