On Jun 21, 2012, at 10:08 AM, Rajith Attapattu wrote:
> Hi All,
>
> Since we are trying to provide a consistent API for all our clients,
> it would be beneficial to have a connection string that can be used
> across all clients.
> This is a topic that has been widely discussed but without much consensus.
>
> The c++ client and python uses a simple scheme.
> It specifies a url which serves as the initial contact point and a
> bunch of options as a map.
> One of those options is reconnect_urls, a comma separated list of urls
> to connect to during failover.
>
> I propose we use the same format for the Java API.
>
> What about JMS ?
> ----------------------------
> We currently use a format that is quite error prone and ugly.
> On the other hand you cannot pass map of options either, everything
> has to be included in String format.
>
> Therefore for JMS I propose the following.
> 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} ...}
>
> 2. For backwards compatibility the old connection URL will be
> supported. It will be parsed and converted into a data structure that
> represents the above.
> (We use a similar strategy for BURL and Address strings in the new code)
>
> What do you folks think?
Excellent stuff. I agree that we need to do 'something' and your plan sounds
right on the money. Backwards compatibility is important as well which you
mention. Let's do it.
Regards,
Weston
>
> Regards,
>
> Rajith
>
> ---------------------------------------------------------------------
> 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]
