Brian Candler wrote:
[private reply intentional?]
Not at all. Trying to use an actual client and I'm failing pretty
consistently.
On Tue, Apr 28, 2009 at 09:52:52AM -0700, Paul Davis wrote:
Me and Robert Newson hashed out some ideas for single instance storage
which he says is used quite a bit by email thingers.
That's a good usage case: incoming mail has RCPT TO:<...> 100 different
recipients, you can store 100 couchdb docs with the same attachment. Users
can then set flags etc on their own copies.
The biggest issue is that the
only real benefit is on disk storage
... which could be quite bit for some usage patterns. Also, I like the idea
of build a git backend on top of this :-)
The second issue is that
you'll only get the benefits after an a compaction.
Not necessarily: if you upload an attachment and find it's already in the
database, there's no need to store it again.
And lastly, without
some changes to the db file format and replication API, there's no way
to not send the entire file on replication.
This is certainly true. But I think you'd probably be changing the db file
format anyway to get this feature.
Regards,
Brian.
