Re: Proton Messenger and the Request/Response pattern

Hi Ted, From my experience I have to agree with you, that the way the request/response is handled in the current API is a bit complicated and caused some troubles to some of our customers connecting to our brokers. But at the same time I like the flexibility of the current approach, where you

Re: [documentation] -- Intro to Proton

Hi Michael, I know you mentioned plans to write some bigger document ... it is not entirely clear to me, whether this is supposed to be a standalone introduction or just a first chapter of the larger document. It suppose the second is correct, right? Also, is it introduction to Proton or just to

Re: example of proton documentation

Hi Michael, I'm rather a foreigner in the land of Proton, but that point of view might make the feedback useful as well :-). As someone who didn't worked with proton much, I would probably raise following questions ... a) If I remember correctly, in (some of) the old Qpid APIs the flow control

Re: Proposed SASL changes (API and functional)

On Wed, Feb 25, 2015 at 7:45 PM, Andrew Stitcher astitc...@redhat.com wrote: If it is ok with them I will copy the comments over there: Alan, Jakub? Sorry, I missed the wiki part. Feel free to copy my comment there if you want.

Re: Proposed SASL changes (API and functional)

Hi Andrew, I'm definitely not a Proton expert, so please excuse me if I missed something. 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

Re: [VOTE] Release RC 3 as Qpid Proton 0.12.0

+1 * I checked the JMS client with 0.12.0-rc3 against MRG-M 3.0 & 3.2 and against Qpid C++ broker (trunk with 0.12.0-rc3) * I checked the Qpid Messaging C++ client build with 0.12.0-rc3 against MRG-M 3.0 and 3.2 On Wed, Feb 10, 2016 at 3:04 PM, Justin Ross wrote: > Hi,

Re: [VOTE] Release Qpid Proton 0.12.0

+1 - I checked the JMS client with 0.12.0-rc against MRG-M 3.2 and against Qpid C++ broker (trunk with 0.12.0-rc) - I checked the Qpid Messaging C++ client build with 0.12.0-rc against MRG-M 3.0 On Wed, Feb 3, 2016 at 4:10 PM, Justin Ross wrote: > The artifacts proposed

Re: Need Help! qpid-cofig: No module named qpid.messaging

I think you need to download and install the Python version of the Qpid Messaging API. You can download it for example here http://qpid.apache.org/components/messaging-api/index.html or on http://qpid.apache.org/download.html. If you don't want to install it into the system directories, it should

Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue

qpid-config is in the qpid-tools package. Go to the download site ( http://qpid.apache.org/download.html) and download the "C++ broker (command-line tools)". It is using the Python version of Qpid Messaging API, so you have to download that as well - it is on the same page. On Fri, Feb 19, 2016

Re: [VOTE] merge the proton mailing list into the users/dev lists

+1 On Wed, Mar 30, 2016 at 1:01 PM, Kai wrote: > +1 > > On Wed, Mar 30, 2016 at 12:25 PM Robbie Gemmell wrote: > > > Hello folks, > > > > Many moons ago, a seperate mailing list was established for Proton, > > back when it was purely a protocol engine

[jira] [Created] (PROTON-363) recv.exe fails on Windows XP because getnameinfo returns WSANO_DATA / error 11004

JAkub Scholz created PROTON-363: --- Summary: recv.exe fails on Windows XP because getnameinfo returns WSANO_DATA / error 11004 Key: PROTON-363 URL: https://issues.apache.org/jira/browse/PROTON-363

[jira] [Created] (PROTON-1139) tx_recv_interactive.py example doesn't work

Jakub Scholz created PROTON-1139: Summary: tx_recv_interactive.py example doesn't work Key: PROTON-1139 URL: https://issues.apache.org/jira/browse/PROTON-1139 Project: Qpid Proton Issue Type