loggerhead as a plugin

[Jonathan Lange]

On Fri, Jan 23, 2009 at 8:24 PM, John Arbash Meinel
<john at arbash-meinel.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martin Pool wrote:
>> I did a little of work picking up from mwh's branch so that loggerhead
>> will work as a plugin.  It's in
>> <https://code.edge.launchpad.net/~loggerhead-team/loggerhead/loggerhead-plugin>.
>>  If you do
>>
>>   bzr branch https://code.edge.launchpad.net/~loggerhead-team/loggerhead/loggerhead-plugin
>> \
>>      ~/.bazaar/plugins/loggerhead
>>
>> then the 'bzr serve' command will get a new --http option, which will
>> run up a loggerhead viewer on branches under the current directory.
>> jml and beuno have a separate patch that lets loggerhead act as a bzr
>> server, and the combination should be pretty nice.
>>
>
> This certainly sounds interesting. My primary concern would be how "bzr
> branch" would interact with the serve that is running. Because if it
> access it via http, at least the default HTTP server in python doesn't
> support range requests, which would cause bzr + pack files to perform
> *very* poorly.
>

It doesn't support range requests[1]. I think the feature is still
useful for LANs / sprints; it just needs a caveat about not using on
production.

jml

[1] bzr gives a warning. The warning says that the server doesn't
support range requests, but doesn't communicate that this will make it
much slower. That means it's not a useful warning to most users.