Eric, Ok, so reading through your reponse twice, I was immediately struck with an idea of MS OneNote for the cloud or Domino (of course). Or would it be Alfresco for the cloud ?
Is that something close to what your building ? What would the users be storing ? Metadata, Document binary attachments ? Everything ? Curious. As far sharing pieces of data.... I do like Google's WAVE, even if it's an early stage. -Thad On Wed, Jul 1, 2009 at 2:56 PM, eric casteleijn < [email protected]> wrote: > [email protected] wrote: > >> Eric, >> >> I like the idea of OAuth incorporated down the line. >> >> Also, It seems as if Brian and yourself are talking more in general about >> a Multi-Tenancy environment within a single CouchDB or is it not as grand of >> an idea yet ? ( "Are we there yet?" ) >> > > I am not sure that multi-tenancy is exactly what we're aiming for, or even > that couchdb itself neatly fits into that terminology, but I'll try to > describe what we are thinking of doing with couchdb: > > Our use case is to have a single couchdb server per user, and (potentially) > many databases for that user within each such server. They will be running > on the end user's system. > > We intend to replicate all of this data between the cloud and all of a > user's registered machines, but only as a means of backup, universal > accessibility (i.e. from the user's work computer and potentially through > the web.) and as a means of sharing pieces of data with other users of the > service. > > If I understand multi-tenancy correctly, that would mean leasing out couch > instances on our hardware, which is only half the story at best: > > I think it's important to stress that *all* the data that is in the cloud > couch instance will be in the users desktop instance as well, and they are > free to do what they want with it. > > In fact they will be able to use the same software to replicate between > computers on their LAN if they do not choose to use our online service at > all, or keep using it without any data loss when they decide to stop using > it. > > -- > - eric casteleijn > http://www.canonical.com >
