On 07/22/2013 06:47 PM, Fraser Adams wrote:
I guess one slight issue is that it might take a bit of time to "have a bit more feedback etc" on things living in /test because it's probably not the first place most users would look and it's not normally "installed" by default so I expect qpidt is only likely to either be "stumbled upon" or possibly found via people noticing it mentioned in discussion threads and then grepped.
Yes, that's a very fair point and I think its probably worth revisiting the discussion around management tooling in general.
I'd tend to agree with the sentiment about having a generic create/delete/list capability though I guess the more generic the more the syntax to control it needs a good manual (we've already had a discussion on relative merits of qpidt vice qpid-ctrl, the latter of which I believe could do the same as qpidt, but is ironically probably *too* generic :-))
Yes, qpid-ctrl can invoke add/delete, but also any other method and at present at least it is therefore a little less intuitive for the simpler stuff. Neither qpid-ctrl nor qpidt are fully polished end-user tools at this point. However I do feel loathe to simply add more stuff to qpid-config without an attempt at some 'genericising'.
Out of curiosity would you be interested if I were to put this sort of behaviour into the GUI?
Very!
There's probably useful scope for having a fairly generic key/value entry page to cater for some of the more "edge-case" queue options, and certainly it might make supporting the currently quite wildly varying queue options between the C++ and Java broker a more tractable problem to solve. Once the stuff is in place to support general key/value queue options it ought to be pretty easy to do the sort of general thing that qpidt allows.
Very much agree. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
