> On Oct. 31, 2013, 12:57 p.m., Kenneth Giusti wrote:
> > Just one small, optional request: the output is not very pretty.  Maybe add 
> > column headers for "name" and "value"?  Or line-wrap the values string?  
> > Again, not essential, but IMHO the current output is a bit hard to read.
> >

Good feedback, thanks! I'll look into some improvements.


- Gordon


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


On Oct. 31, 2013, 8:20 a.m., Gordon Sim wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15083/
> -----------------------------------------------------------
> 
> (Updated Oct. 31, 2013, 8:20 a.m.)
> 
> 
> Review request for qpid, Justin Ross, Kenneth Giusti, Jakub Scholz, and Ted 
> Ross.
> 
> 
> Bugs: QPID-5277
>     https://issues.apache.org/jira/browse/QPID-5277
> 
> 
> Repository: qpid
> 
> 
> Description
> -------
> 
> The qpid-config utilty currently allows queues, exchanges and bindings to be 
> created, but doesn't support other types.
> 
> Having a generic mechanism for create, delete and list would be very useful 
> as it would mean the tool could be used for any entity types added (even if 
> optional). Specifically this would eliminate the need for the current qpidt 
> test utility in managing the various new 1.0 related entities.
> 
> With attached patch you can do e.g.
> 
> qpid-config add domain my-domain --argument url=localhost:6666 
> qpid-config list domain
> qpid-config del domain
> 
> The existing functions and options of qpid-config are not altered.
> 
> 
> Diffs
> -----
> 
>   /trunk/qpid/tools/src/py/qpid-config 1537051 
>   /trunk/qpid/tools/src/py/qpidtoollibs/broker.py 1537051 
> 
> Diff: https://reviews.apache.org/r/15083/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Gordon Sim
> 
>

Reply via email to