There isn't a way to do this as yet, it it's something that I had in the
back of my mind.
I'm a little torn, so there's a couple of approaches and they both have
merits. At the moment there's a "-a" option to specify a default broker
and there's a mechanism to add connections on the GUI.
One slight "complication" is that the way I've designed it is that the
GUI behaves very much like a QMF Console connection and the REST API is
really just a proxy, so the default is a default URL as opposed to a
default connection, the GUI is responsible for asking the REST API to
create a connection on its behalf.
So what does that mean. Well specifying a "properties file" is something
that is "server side" so it's possible to have the browser "discover" as
set of default URLs available so it's something I might look at. However
I quite like (and I think favour) the idea of being able to persist the
GUI config "client side" so something like HTML5 local storage or even
good old cookies.
It's something I'll have a think about - hopefully you can see given the
nature of potentially having lots of clients connect to arbitrary
brokers via different GUI instances it's not totally trivial to do this
in a way that's consistent with some of the design goals that I had for
myself.
To be fair one other possibility could make use of security principals,
so all the state in the system actually relates to the connection name,
but internally I also use the principal to make really sure that these
names are unique. That got me thinking that it's be possible to have
config on the server side that whilst it may not relate to a specific
client instance it does relate to a particular user name.
I still like the idea of storing config on the browser, but there's a
few options. I'll have a think :-)
P.S. glad you like the GUI :-) it's really nice that a couple of people
have referred to it as "amazing". An awful lot of work has gone in to it
so it's great that people are starting to play with it and come up with
ideas.
Out of curiosity have you found it pretty responsive? Bruno Matos has
mentioned that he's seen things take a while to update, I'm a bit
baffled by this 'cause that's something I've never come across - I get
updates pretty much regular as clockwork every 10 seconds and if I look
on the brokers page the uptime increases by ~10s every 10s and similarly
if I look at the graphs for the QMF connections they are regularly
updating. What's your experience here?
Cheers,
Frase
On 29/01/13 08:56, Zhemzhitsky Sergey wrote:
Hi Fraser,
Amazing GUI! Thanks a lot!
I'm wondering whether there is a possibility to specify all the brokers to
connect to in a properties file, i.e.
config.properties
broker.default=guest/guest@host1:5672
broker.name2=guest/guest@host2:5672
broker.name3=guest/guest@host3:5672
broker.default.hide.qmf.objects=true
broker.name2.hide.qmf.objects=false
broker.name3.hide.qmf.objects=true
So all this brokers will be displayed just after restarting of the GUI under
the names specified in the properties file.
Best Regards,
Sergey
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
