I had an idea of how we can implement this without signficant burden on the app server with current releases of bzr. We only need to serve 3 files without any HTTP redirects:
* .bzr/branch-format with contents "Bazaar-NG meta directory, format 1"
* .bzr/branch/format with contents "Bazaar-NG Branch Reference Format 1"
* .bzr/branch/location with the HTTP URL of the branch.
I just tried putting this simple file structure on a local web server, and I was able to branch from it successfully. The recorded parent branch was the real Bazaar branch rather than the branch reference I created.
I had an idea of how we can implement this without signficant burden on the app server with current releases of bzr. We only need to serve 3 files without any HTTP redirects:
* .bzr/branch-format with contents "Bazaar-NG meta directory, format 1" location with the HTTP URL of the branch.
* .bzr/branch/format with contents "Bazaar-NG Branch Reference Format 1"
* .bzr/branch/
I just tried putting this simple file structure on a local web server, and I was able to branch from it successfully. The recorded parent branch was the real Bazaar branch rather than the branch reference I created.
So this should result in the bzr client making 3 requests to https:/ /launchpad. net when creating the branch, with all further requests going to http:// bazaar. launchpad. net/.