Ken Giusti created PROTON-301:
-
Summary: Add a valgrind-based test to the SSL unit tests.
Key: PROTON-301
URL: https://issues.apache.org/jira/browse/PROTON-301
Project: Qpid Proton
Issue Type: Te
[
https://issues.apache.org/jira/browse/PROTON-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-78.
--
Resolution: Fixed
Assignee: Ken Giusti (was: Rafael H. Schloming)
Each ssl unit test will throw t
[
https://issues.apache.org/jira/browse/PROTON-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-299.
---
Resolution: Fixed
Good find - fix checked into trunk:
http://svn.apache.org/viewvc?view=revision&rev
On 04/22/2013 09:31 AM, Rafael Schloming wrote:
This might seem like an odd way to fail link establishment, however it is
really a special case of a more general negotiation pattern, for example
the same pattern might be used to do a kind of redirect:
Client ATTACH(target="old-queu
On Mon, Apr 22, 2013 at 09:31:09AM -0400, Rafael Schloming wrote:
> To understand this, it's helpful to think in terms of which state is
> associated with the transport layer and which is associated with the
> application layer. It also helps to think in terms of communication
> endpoints, i.e. an
To understand this, it's helpful to think in terms of which state is
associated with the transport layer and which is associated with the
application layer. It also helps to think in terms of communication
endpoints, i.e. an entity capturing the relevant state for a given
communication layer. The l
In reading through the AMQP 1.0 specification, I have some (probably
fundamental) questions about the spec. Specifically, what is purpose of
establishing a link on a session that has either no source or not
target (or neither source nor target) set? In the spec it says that such
links will never pr
