Why can't these just be specified as key=value options? Scheme is something of a namespace which introduces totally new semantics; we shouldn't modify the scheme just because some behavior here may be different
?couchbase2x=true Also note what I said before regarding what the scheme is actually used for. On May 24, 2014, at 1:50 PM, Aliaksey Kandratsenka <[email protected]> wrote: > > > > On Sat, May 24, 2014 at 1:44 PM, Mark Nunberg <[email protected]> wrote: > +1 on the JDBC format: > > http://lists.mysql.com/cluster/249 > > MySQL cluster does this as well. > > I'd also like to mention that libcouchbase will be included in this spec. > Client libraries wrapping libcouchbase will be responsible for parsing out > any client-specific settings in the string, and then passing the rest of the > string to libcouchbase, which will then go ahead and parse it. > > Just a note though; you don't actually need a URI scheme here JDCB and > friends use the URI scheme to locate the driver to load. However the > couchbase:// stuff is implicit. > > Do not remove scheme please. It can still carry important information e.g.: > > couchbase:// - default behavior > > couchbase+ssl:// - default on top of ssl for rich and paranoid > > couchbase2x:// - (imaginary of course) for 2.x clusters > > couchbase+dns-srv:// > > The list can go on. > > > -- > You received this message because you are subscribed to the Google Groups > "Couchbase" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
