Binary file storage similar to Kiln

[John Meinel]

http://Launchpad.net/bzr-keywords
Uses the content filter code.

I wonder if you'll actually rather have 2 files. Foo.meta and Foo.dat. And
when we read/write Foo.meta you play with Foo.data which is otherwise
ignored.

It seems cleaner to me, at least.
John
=:->
On Jul 22, 2011 10:47 PM, "Anteru" <newsgroups at catchall.shelter13.net>
wrote:
> Hi,
>
>> You could write a content filter that would have the 'canonical' form be
>> the hash of the file, and the 'convenient' form be the expanded content.
> thanks. I just browsed the docs, this seems at least like a good
> starting point. Is there some example of a content filter somewhere? I
> checked my locally installed plugins, and there doesn't seem to be any.
>
> Assuming I get the content filter working, I would change the read
> operation to fetch the actual file from the server and the write to
> store only the hash plus transferring the file contents if the hash is
> not yet known on the server side. For this, I need communication with
> the server. Is it possible to hook the bzr transport layer for this? Or
> should I make that completely separate and use my own transport method?
>
> Cheers,
> Anteru
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110723/af33f04f/attachment.html>