Hey Guys,

I have updated the proposal to use a URI-like formatting.  It additional 
specifies the semantics of the various scheme's (note that using SRV is not 
considered another scheme).
https://docs.google.com/document/d/172ausWsYt3eYYOZ1lYHVS8ccbrrVJaGwHIRsf_O_Hyc

Please provide any and all feedback!  I'm hoping to be able to move this 
proposal out of DRAFT status by the end of the week!

Cheers, Brett
[Couchbase Logo]
Always Scalable, Always On NoSQL

________________________________

        Brett Lawson
SDK Developer

Email: [email protected]



From: Aliaksey Kandratsenka 
<[email protected]<mailto:[email protected]>>
Date: Tuesday, May 27, 2014 at 4:52 PM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Cc: Michael Nitschinger 
<[email protected]<mailto:[email protected]>>, 
Matt Ingenthron <[email protected]<mailto:[email protected]>>, Brett Lawson 
<[email protected]<mailto:[email protected]>>, Sergey Avseyev 
<[email protected]<mailto:[email protected]>>, Jeffry Morris 
<[email protected]<mailto:[email protected]>>
Subject: Re: Proposal for bootstrap and connection string clarification.




On Tue, May 27, 2014 at 12:40 PM, M. Nunberg 
<[email protected]<mailto:[email protected]>> wrote:
Yep. I guess I can agree with that; so we'd have couchbase:// and 
couchbase+dnssrv:// -- but i think those would be it?

Not necessarily. But most importantly is that it proves that we should not omit 
scheme.

Other things that might be different namespaces is whether you're specifying 
memcached endpoint (for cccp) or http endpoint. It doesn't look like CCCP is a 
fully "done deal" given that people are asking more from it which it does not 
currently have and given http is capable of solving problem as well.

-- 
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.

Reply via email to