> On Oct. 25, 2013, 2:08 p.m., Kenneth Giusti wrote:
> > I like this approach.  One question - I may have missed this in the patch - 
> > but does the ACL configuration regarding the ability to create 
> > queues/exchanges apply to these operations too?   (I suspect so).

Depends what you mean... if a matching queue policy exists for an incoming 
link, then a queue will be created and that will require ACL permissions. 
However creating the queue policy itself is distinct. At present there is no 
explicit permission for that entity, but you would need the ability to invoke 
QMF methods etc in order to create them.


- Gordon


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14882/#review27533
-----------------------------------------------------------


On Oct. 23, 2013, 7:56 p.m., Gordon Sim wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14882/
> -----------------------------------------------------------
> 
> (Updated Oct. 23, 2013, 7:56 p.m.)
> 
> 
> Review request for qpid, Kenneth Giusti and Ted Ross.
> 
> 
> Bugs: QPID-5251
>     https://issues.apache.org/jira/browse/QPID-5251
> 
> 
> Repository: qpid
> 
> 
> Description
> -------
> 
> This adds the ability to create QueuePolicy or TopicPolicy instances that 
> enable on demand creation of queues or topics respectively for any name that 
> fails to resolve to an existing queue/exchange/topic and matches the pattern 
> on a defined policy.
> 
> The primary mechanism for managing these policies is through the QMF 
> create/delete methods. E.g using the qpidt utility:
> 
>   qpidt create QueuePolicy dynamic-queue-*
> 
> will create a queue policy with the pattern dynamic-queue-*, so that any 
> attempt to link to a node that matches that pattern (i.e. starts with 
> dynamic-queue-), e,g, dynamic-queue-abc, will result in the queue being 
> created on demand. Other options can be specified for the policy and those 
> will be used when creating the node.
> 
> In addition I've added a couple of 1.0 related command line options to qpidd 
> - queue-pattern and topic-pattern - so that for the simple cases you can 
> specify the desired behaviour when starting qpidd up. E.g. 
> 
>  ./src/qpidd --auth no  --load-module ./src/amqp.so --queue-pattern 
> 'dynamic.\queues\.*' --topic-pattern 'dynamic\.topics\.*'
> 
> 
> Diffs
> -----
> 
>   /trunk/qpid/cpp/src/amqp.cmake 1535048 
>   /trunk/qpid/cpp/src/qpid/broker/amqp/BrokerContext.h 1535048 
>   /trunk/qpid/cpp/src/qpid/broker/amqp/BrokerContext.cpp 1535048 
>   /trunk/qpid/cpp/src/qpid/broker/amqp/NodePolicy.h PRE-CREATION 
>   /trunk/qpid/cpp/src/qpid/broker/amqp/NodePolicy.cpp PRE-CREATION 
>   /trunk/qpid/cpp/src/qpid/broker/amqp/ProtocolPlugin.cpp 1535048 
>   /trunk/qpid/cpp/src/qpid/broker/amqp/Session.cpp 1535048 
>   /trunk/qpid/cpp/src/qpid/broker/amqp/Topic.h 1535048 
>   /trunk/qpid/cpp/src/qpid/broker/amqp/Topic.cpp 1535048 
>   /trunk/qpid/cpp/src/qpid/sys/regex.h 1535048 
>   /trunk/qpid/specs/management-schema.xml 1535048 
> 
> Diff: https://reviews.apache.org/r/14882/diff/
> 
> 
> Testing
> -------
> 
> Minimal.
> 
> 
> Thanks,
> 
> Gordon Sim
> 
>

Reply via email to