On May 24, 2014, at 00:43 , Brett Lawson <[email protected]> wrote:
> Any and all input is welcome, specifically in regards to theOpen Questions
> which are described in the document.
> Open Questions
> * Should we include whether SSL is enabled or not in the connection
> string, or have it as a seperate property outside the connection string (ex:
> `host1;host2;ssl=on` or `host1;host2?ssl`)?
> * Should we use some kind of true 'connection string' format, such as
> JDBC or ODBC DSN strings (ex:
> `couchbase://host1,host2,host3?ssl=on&sslmode=required)?
Gentlefolk,
After taking off my shiny mobile developer hat and putting on my
scruffy, beat up enterprise server architect hat, allow me to opine on your
fine proposal.
> Should we include whether SSL is enabled or not in the connection string, or
> have it as a seperate property outside the connection string (ex:
> `host1;host2;ssl=on` or `host1;host2?ssl`)?
Whether secure communications are available should be something that is
easy to determine. IOW, the very first response should say whether security can
be turned on. This maximizes the likelihood that security will be used and
minimizes the chance of inadvertent information disclosure. Security is not an
afterthought. CB will be used to store sensitive information in a multi-tier
architecture. It must be easy to define and USE separate security zones behind
the firewall. Reducing protocol friction helps this process. (How's that for
fancy pants enterprise architect-speak? I've still got it. ;-)
> Should we use some kind of true 'connection string' format, such as JDBC or
> ODBC DSN strings (ex: `couchbase://host1,host2,host3?ssl=on&sslmode=required)?
One of the strengths of Couchbase is due to its roots derived from
CouchDB. Couch technologies share a few key values. One of which is the use of
web protocols, such as URI schemes. While I cannot say how such a string might
be used in the future, having it fall into the pattern used by other resource
descriptors is likely to be a "good thing" and map into standard web libraries
on every platform. As you have already defined the 'couchbase:' scheme (as I
see it in my cbbackup and cbrestore scripts), I would encourage you to continue
to use it and expand its semantic value. Defining a new syntax is unlikely to
have much leverage and just require mostly pointless new code on every platform.
Anon,
Andrew
____________________________________
Andrew W. Donoho
Donoho Design Group, L.L.C.
[email protected], +1 (512) 666-7596, twitter.com/adonoho
Download Retweever here: <http://Retweever.com>
No risk, no art.
No art, no reward.
-- Seth Godin
--
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.
