I noticed another discrepancy with regards to the option separator. The documentation says it is "&" . <Exchange Class>://<Exchange Name>/[<Destination>]/[<Queue>][?<option>='<value>'[&<option>='<value>']]
But the Test cases and the implementation check for comma. And then in the URLHelper.printOptions method, it prints the URL using "&" as the option separator. We need to decide on a consistent set of rules for the Binding URL. For now I have added support for both comma and ampersand. Regards, Rajith On Tue, Feb 26, 2008 at 5:56 PM, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > Hi All, > > Based on the current URL format documented at > http://cwiki.apache.org/qpid/bindingurlformat.html, both the destination > and queueName is optional. > However the following URL format leads to some issues. > > <Exchange Class>://<Exchange > Name>/[<Destination>]/[<Queue>][?<option>='<value>'[&<option>='<value>']] > > If both destination and queueName are specified or if the user specifies > one the following formats then it is fine. > topic://amq.topic/myDest/?option='1' > direct://amq.direct//myQueue?option='1'. > > However if a user specifies the following then it is difficult to figure > out whether he intended to specify the destination or queueName. > direct://amq.direct/mydest?option='1'. > Based on the documentation this is legal. > > We need to make this less ambiguous to the end user. > I propose that we always interpret the following format as QueueName > direct://amq.direct/mydest?option='1'. > If the user wants to only specify destination then they must explicitly > use the following format. > topic://amq.topic/myDest/?option='1' > > Comments and suggestions are most welcomed. > Besides can somebody please explain what the destination really means? and > also how it used? > > -- > Regards, > > Rajith Attapattu > Red Hat > blog: http://rajith.2rlabs.com/ -- Regards, Rajith Attapattu Red Hat blog: http://rajith.2rlabs.com/
