On 11 Dec 2008, at 22:12, David Schoonover wrote:
The wishlist is long, but the two missing killer features for me are:
- Native Erlang API
You can already use the internal API, but it is going to be changed
and polished
for 1.0.
- DB Sharding
(CouchDB)-client sharding is possible today. DB partitioning
transparent to a
client is not planned for 1.0.
Cheers
Jan
--
On Thu, Dec 11, 2008 at 4:02 PM, Antony Blakey <[email protected]
> wrote:
On 12/12/2008, at 7:28 AM, Damien Katz wrote:
On Dec 11, 2008, at 3:43 PM, Chris Anderson wrote:
On Fri, Dec 5, 2008 at 2:30 PM, Damien Katz <[email protected]>
wrote:
Yes yes yes! This is exactly how it should work, pull all the
docs in a
single http request and also record the last seq num. Then later
incrementally pull new changes using the seq num, lather rinse
repeat.
Restore by POSTing the docs in bulk updates.
With the same view (_all_docs_by_seq with super_include_docs),
could
recipient-triggered replication be accomplished in a single HTTP
request? This might speed up replication a bunch as well.
I'm thinking of removing the _all_docs_by_seq HTTP view and
replacing it
with something that will allow for more flexibility and also allow
for Comet
like events, by providing a filter function that finds documents
that meet a
criteria, and to be notified immediately when new documents are
saved that
meet that criteria. This is meant to be used by the replicator and
external
indexers, but to also try to make it be like a regular view and
while
supporting all the other stuff is pointlessly complex.
Mmmm, tasty!
Antony Blakey
--------------------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787
Success is not the key to happiness. Happiness is the key to success.
-- Albert Schweitzer
--
LOVE DAVE
