H. Peter Anvin wrote:
Shawn O. Pearce wrote:
Funny you say that. This was a GSoC 2008 project idea. We even
received an application from a student for it.
The hard part is either making the server side stateful, so it can
remember what the last RCP call had said it wants/haves, or doing a
stateless protocol where the client uses an exponential expansion
(or some such behavior) of its have list until the server replies
with the pack data.
One easy way of doing the former is to have a session reassociator in
the flow; pretty much a multiplexer which receives the HTTP request, and
passes it onto a work slave (which can be an ordinary process, in fact,
can be the ordinary git daemon) based on a session and sequence ID.
s/multiplexer/demultiplexer/
The best might be to turn the demultiplexer either into an Apache module
or some scripting language which can run inside Apache (e.g. mod_perl)
to avoid Apache spawning a CGI program which is only used to talk to the
git daemon backend.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
