I totally agree with Gordon here. Most url start with <protocol>://<host>:<port>?<params> And we seem to differ from the norm which makes it harder to remember.
Also having a brokerlist will be redundent when we introduce a solution for https://wiki.108.redhat.com/jira/browse/AMQP-95 The JIRA talks about a broker informing clients about possible candidates to use in the event a failover happens. This list is handed over when the client connects to the broker. (Thanks Rafi for pointing this out) Also if you use a smart cluster which does transparent failover, then the client only needs to use a single url. When AMQP-95 gets voted in the above URL scheme will need to change as the additonal information is not needed. Regards, Rajith On 7/26/07, Gordon Sim <[EMAIL PROTECTED]> wrote:
Martin Ritchie wrote: > Is this url really too difficult for your users to understand? > > amqp://guest:[EMAIL PROTECTED]/virtualhost?brokerlist='localhost' Personally I find that syntax a little odd and unintuitive; it seems to emphasise what I would consider secondary values over what I would consider the more important and generally relevant ones. My mind is accustomed to the host and port being in the first part of a URL, rather than appended as query string parameters. This example doesn't fit into any pattern I'm familiar with which makes it harder to remember and takes more effort to parse it in my head. That doesn't mean its wrong of course, but since the topic came up I thought I'd toss my 2 cents in(!).
