delta/python-packages/qpid-python.git/cpp/src/qpid/broker/ConnectionHandler.cpp, branch QPID-6125-ProtocolRefactoring

QPID-3921: Refactored Broker::Options into its own independent class

2014-07-01T19:12:38+00:00

- Now called BrokerOptions
- Added extra getters to Broker so that nothing else needs to know
  about BrokerOptions
- Significantly reduces header coupling as lots of files include
  Broker.h, but now don't need Options.h

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1607166 13f79535-47bb-0310-9956-ffa450edef68

QPID-5621: [C++ broker] userId is not passed to ACL when DIGEST-MD5 is used while creating link

2014-03-11T09:40:08+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1576248 13f79535-47bb-0310-9956-ffa450edef68

QPID-5599: C++ Broker silently ignores --max-connections option when no ACL file is loaded

2014-03-05T02:33:46+00:00

Simply installing a null and permissive rule file trips up the 'create link'
security check. The security check from 
https://issues.apache.org/jira/browse/QPID-4631 reasons that if authentication
is enabled and no ACL rule file is specified then interbroker links are 
denied. The check for 'ACL rule file is loaded' is simply the existence of
the ACL object. That check is voided by always having an ACL object regardless
of whether the ACL rule file was specified or not.

One fix considered was adding an ACL rule "acl deny-log all create link" to
the formerly null rule set when no ACL file is specified. This solution has
too much complexity in several places and is too hard.

The fix implemented here is a boolean flag indicating if the ACL rule set 
in force is specified by the user or not. Then the security check tests
that the acl exists (always true) and that the rule set is specified by the
user. 



git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1574291 13f79535-47bb-0310-9956-ffa450edef68

QPID-4712: fixes for windows, rhel5

2013-06-25T17:18:38+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1496545 13f79535-47bb-0310-9956-ffa450edef68

QPID-4712: authorisation for AMQP 1.0 connections

2013-06-25T13:28:15+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1496466 13f79535-47bb-0310-9956-ffa450edef68

QPID-4905: Tidy up broker::Connection

2013-06-19T14:26:03+00:00

- Clean up code for accounting for sent frames
- merged Connection and ConnectionState into Connection

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1494639 13f79535-47bb-0310-9956-ffa450edef68

QPID-4905: Remove unused Connection ErrorListener interface

2013-06-10T19:46:59+00:00

- was only used by removed cluster support

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1491584 13f79535-47bb-0310-9956-ffa450edef68

QPID-4905: Remove deprecated and unused federation property

2013-06-10T19:46:48+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1491581 13f79535-47bb-0310-9956-ffa450edef68

QPID-4631: C++ Broker federated links are protected by ACL policy.

2013-04-29T14:49:31+00:00

This issue evolved a bit between the original discussion and the final
commit. See https://reviews.apache.org/r/10658/ for the details.



git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1477112 13f79535-47bb-0310-9956-ffa450edef68

QPID-4748: Consistent handling of durations in broker configuration, allowing sub-second intervals.

2013-04-19T02:00:16+00:00

Provides string conversion for sys::Duration, allowing intervals to be expressed like this:

10.5 - value in seconds, backward compatible.
10.5s - value in seconds
10.5ms - value in milliseconds
10.5us - value in microseconds
10.5ns - value in nanoseconds

Converted the folllowing broker options to Duration:
mgmtPubInterval, queueCleanInterval, linkMaintenanceInterval, linkHeartbeatInterval

Did not convert: maxNegotiateTime. This is expressed in milliseconds so it would not be
backward compatible to make it a Duration.

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1469661 13f79535-47bb-0310-9956-ffa450edef68