post 0.8 development

[John A Meinel]

Matthieu Moy wrote:
> Robert Collins wrote:
> 
>> Really, do deal with latency here, solve the root cause :). Either make
>> the branch list opaque to the user, not a real directory on disk, so
>> that a system maintained compact list of branches is doable, or
>> eliminate the multiplying latency cost via async requests or a smart
>> server.
> 
> With a smart server, only one request is sufficient :
> 
> - Hi, pls give me the list of branches !
> [ smart server does a recursive exploration server-side ]
> - OK, here it is : ...
> 
> For HTTP, there could be a simple PHP/CGI script doing that.
> 
> One argument in favor of this is that "browse" won't be used very often,
> so it's not necessarily dramatic if it's slow under some circumstances.
> 
> (I'm not yet 100% convinced by either approach, but bringing my 2cents)
> 

I will say that Aaron's 'bzr branches' command gives all sorts of http
error logs. (Especially if you have a working tree).
But it is actually fairly fast, even over http. I would say it is on par
with Arch's browse commands.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060510/7d0a6ddd/attachment.pgp