Hi Piotr, see comments in-line:
- Original Message -
> From: "Piotr Kliczewski"
> To: "Ken Giusti"
> Cc: proton@qpid.apache.org, "Saggi Mizrahi" , "Barak
> Azulay"
> Sent: Friday, March 28, 2014 6:56:08 AM
> Subject: R
t;Ken Giusti"
To: proton@qpid.apache.org, "Saggi Mizrahi"
Cc: "Piotr Kliczewski" , "Barak Azulay"
Sent: Thursday, January 23, 2014 3:24:00 PM
Subject: Re: Protocol detection
Hi Saggi
Sounds like you need to handle all the socket i/o directly, rather than having
On Thu, Jan 23, 2014 at 12:07 PM, Barak Azulay wrote:
> Thanks ken,
> This looks very helpful - we will try it.
>
> In addition - who can we talk to about the java binding for qpid-proton
> (AMQP 1.0),
>
What would you like to know?
--Rafael
: "Piotr Kliczewski" , "Barak Azulay"
>
> Sent: Thursday, January 23, 2014 4:24:00 PM
> Subject: Re: Protocol detection
>
> Hi Saggi
>
> Sounds like you need to handle all the socket i/o directly, rather than
> having Proton do it "under the covers
Hi Saggi
Sounds like you need to handle all the socket i/o directly, rather than having
Proton do it "under the covers", right?
To do this, you'll need to avoid using the Driver and Connector and Listener
classes from the Python binding - these classes perform all socket management
and I/O, fo
