- Original Message -
From: Dominic Evans dominic.ev...@uk.ibm.com
To: proton@qpid.apache.org
Sent: Wednesday, April 1, 2015 1:55:08 PM
Subject: Re: Idle Timeout of a Connection
-Ken Giusti kgiu...@redhat.com wrote: -
I've gone back and forth about what the proper
2.4.5 Idle Timeout Of A Connection
To avoid spurious timeouts, the value in idle-time-out SHOULD be half the
peer's actual timeout threshold
So, to me, this means on the @open performative the client should flow (e.g.,)
3 as the idleTimeOut it would like to negotiate, but should actually
-Rafael Schloming r...@alum.mit.edu wrote: -
On Wed, Apr 1, 2015 at 6:00 AM, Dominic Evans dominic.ev...@uk.ibm.com
wrote:
2.4.5 Idle Timeout Of A Connection
Thoughts?
I believe your interpretation is correct. I've certainly noticed idle frames
being sent significantly more
On Wed, Apr 1, 2015 at 6:00 AM, Dominic Evans dominic.ev...@uk.ibm.com
wrote:
2.4.5 Idle Timeout Of A Connection
To avoid spurious timeouts, the value in idle-time-out SHOULD be half the
peer's actual timeout threshold
So, to me, this means on the @open performative the client should flow
Timeout of a Connection
-Rafael Schloming r...@alum.mit.edu wrote: -
On Wed, Apr 1, 2015 at 6:00 AM, Dominic Evans dominic.ev...@uk.ibm.com
wrote:
2.4.5 Idle Timeout Of A Connection
Thoughts?
I believe your interpretation is correct. I've certainly noticed idle
-Ken Giusti kgiu...@redhat.com wrote: -
I've gone back and forth about what the proper behavior should be for
Proton re: idle timeout.
It's that darn pesky SHOULD... which means 'recommended', not
exactly 'required'.
Yes, I was similarly surprised that the spec chose to say 'SHOULD'
the build, there is a compilation
failure which according to Jenkins would seem to be from the above:
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/855/
[PATCH] proton-j: no way to implement idle timeout of a connection
6f2105d41ddbbddac9043b47aa23559e5b77380c in qpid-proton's branch
refs/heads/master from [~dnwe]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=6f2105d ]
PROTON-811: fix RememberingTransportInput compile
[PATCH] proton-j: no way to implement idle timeout of a connection
better now:
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/857/
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira
to the PROTON-811 JIRA
Closes #8
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
Project: Qpid
with
the error message of encountered a null which is not a interface
org.apache.qpid.proton.amqp.transport.FrameBody
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL
to the PROTON-811 JIRA
Closes #8
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
Project: Qpid
at:
https://github.com/apache/qpid-proton/pull/8
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
request:
https://github.com/apache/qpid-proton/pull/8#issuecomment-75039668
Looks good to me.
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https
request:
https://github.com/apache/qpid-proton/pull/8#issuecomment-75039802
@rhs thanks
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https
a
separate catch to ignore it. It seems cleaner to add a position()
accessor to the TransportInput interface that handles closed streams
in the same way as capacity(), without throwing the RuntimeException
[PATCH] proton-j: no way to implement idle timeout of a connection
timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
Project: Qpid Proton
Issue Type: Bug
Components: proton-j
Affects
idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
Project: Qpid Proton
Issue Type: Bug
Components: proton-j
for the
SASL object always set SASL client mode when run against the Java shims, and
this breaks the TestServer - but my lack of Python expertise stopped me getting
any further).
[PATCH] proton-j: no way to implement idle timeout of a connection
it in the Connection object. If we could resolve this difference then
it would be pretty straightforward to enable the portion of the shim that deals
with idle timeouts and get added test coverage from the python test suite.
[PATCH] proton-j: no way to implement idle timeout of a connection
with an implementation of Transport.tick(long) that is much
closer to the proton-c implementation.
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org
a timeout over an absolute value? (If there
is, I'd say keep it as is.)
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse
-work based on the C code.
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
Project: Qpid Proton
idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
Project: Qpid Proton
Issue Type: Bug
Components: perl-binding
Adrian Preston created PROTON-811:
-
Summary: [PATCH] proton-j: no way to implement idle timeout of a
connection
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
Project: Qpid
to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON-811
Project: Qpid Proton
Issue Type: Bug
Components: proton-j
has happened, so
providing a slightly more abstract interface and letting the Transport
implementation decide when it needs to do something and what exactly it needs
to do would be preferred.
[PATCH] proton-j: no way to implement idle timeout of a connection
have a go at reworking the patch, as per your
suggestions.
[PATCH] proton-j: no way to implement idle timeout of a connection
--
Key: PROTON-811
URL: https://issues.apache.org/jira/browse/PROTON
28 matches
Mail list logo
