All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@kernel.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>,
	ftpadmin <ftpadmin@kernel.org>
Subject: Re: Corporate firewall braindamage
Date: Thu, 10 Apr 2008 18:03:32 -0700	[thread overview]
Message-ID: <47FEB8E4.3070306@kernel.org> (raw)
In-Reply-To: <47FEA7AE.1050403@zytor.com>

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

  reply	other threads:[~2008-04-11  1:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 21:11 Corporate firewall braindamage H. Peter Anvin
2008-04-10 23:14 ` Junio C Hamano
2008-04-10 23:33   ` Shawn O. Pearce
2008-04-10 23:50     ` H. Peter Anvin
2008-04-11  1:03       ` H. Peter Anvin [this message]
2008-04-11  8:25   ` david

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47FEB8E4.3070306@kernel.org \
    --to=hpa@kernel.org \
    --cc=ftpadmin@kernel.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.