On Mon, 2007-01-08 at 06:33 -0800, [EMAIL PROTECTED] wrote: > Page Edited : qpid : BindingURLFormat BindingURLFormat has been edited > by Martin Ritchie (Jan 08, 2007). > > (View changes) > > Content: > <Exchange Class>://<Exchange > Name>/[<Queue>][?<option>='<value>'[&<option>='<value>']] > snip
> Examples > direct://amq.direct/SimpleQueue > direct://amq.direct/UnusuallyBoundQueue?routingkey='queue' > topic://amq.topic?routingkey='stocks.#' > topic://amq.topic?routingkey='stocks.nyse.ibm' Using exchange types as the protocol prefix of a URL is a bad idea, you would never be able to standardize it with IANA or whoever monitors these things. The set of exchange types is open to change in the future but URL protocol prefixes must be unique forever. Also this format abuses the prefix://host/path convention for internet protocols. I'd suggest something like: qpid://<host>[:<port>]/<exch class>:<exch name>/[etc. as above] Long term we'll want vendor neutral standard AMQP URLs like: amqp:... But it would be a mistake to try to grab the amqp: prefix right away. That would make transition to standard AMQP URL's *more* difficult in the future because we'd have no easy way to distinguish between an AMQP standard URL and an old qpid-proprietary URL for backwards compatibility. Cheers, Alan.
