On Thu, Jun 21, 2012 at 12:16 PM, Gordon Sim <[email protected]> wrote:
> On 06/21/2012 03:08 PM, Rajith Attapattu wrote:
>>
>> 1. A connection string that contains a URL and an optional list of
>> properties (for connection options) using the same syntax as address
>> strings
>> url ; {k1:v1, k2 :{k1:v1} ...}
>
>
> As I recall, the existing "connection URL" as supported by the JMS client
> has both 'top level' options that apply whichever broker is in use and
> 'broker url' options that are in effect only for connections to that
> specific broker.
This is indeed a problem area, all though in practise I don't think
it's widely used or even useful.
Could anybody who use this particular feature elaborate a bit more on
the use cases ?
Some concrete examples of it's usefulness will certainly help us
understand if we need to accommodate this or not.
In the event it's needed, we could resort to something like the following...
url; {k1:v1, reconnect_urls : { url; {options}, url; {options...}... }... }
>From a parser pov it's simple, but I'm quite keen to avoid this if possible.
> The mapping from that to your scheme above is not obvious (though the are
> clearly ways in which it could be done).
>
> I think more detail on use cases to be supported is needed.
Agreed!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
