Giusti kgiu...@redhat.com
To: proton@qpid.apache.org, Saggi Mizrahi smizr...@redhat.com
Cc: Piotr Kliczewski pklic...@redhat.com, Barak Azulay
bazu...@redhat.com
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
: Protocol detection
Ken,
I use your sample and currently I am working on clean up code.
In my case the closure is initiated by the client and I close all links then
connection and socket at the end.
When client socket is closed the server calls:
close_input function which invokes
/display/qpid/Proton+Architecture
- Original Message -
From: Saggi Mizrahi smizr...@redhat.com
To: proton@qpid.apache.org
Cc: Piotr Kliczewski pklic...@redhat.com, Barak Azulay
bazu...@redhat.com
Sent: Wednesday, January 22, 2014 7:03:37 AM
Subject: Protocol detection
Hi, I'm from
On Thu, Jan 23, 2014 at 12:07 PM, Barak Azulay bazu...@redhat.com 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
Hi, I'm from the VDSM project which is part of oVirt.
We are in the process of adding multiple protocol support
one of which is AMQP 1.0 though the proton library.
We want to keep only requiring one port so our solution is
to peek at the stream, detect the protocol and then pass
it to the proper
