Re: If you would write git from scratch now, what would you change?

From: Shawn O. Pearce <spearce@spearce.org>
Date: Nov 27, 2007, 01:58 UTC
Message-ID: <20071127015833.GL14735@spearce.org>
In-Reply-To: <fifstd$ilj$1@ger.gmane.org>

Jakub Narebski <jnareb@gmail.com> wrote:

Show 12 quoted lines

> Shawn O. Pearce wrote:
> 
> [git-gui in XUL]
> 
> > But XUL doesn't support launching a process and connecting pipes
> > to its stdin and stdout.  I started to try and create an XPCOM
> > extension to provide that functionality from NSPR and started to
> > run into major problems compiling the XPCOM plugin, getting the
> > necessary interfaces implemented, etc.
> 
> What about Ajax / Comet support in XUL, Can this be used for that?
> (Just an [perhaps stupid] idea).

Yes, XUL fully supports AJAX. If it didn't Google Maps and its cool interface wouldn't exist. :-)

The problem there is that AJAX requires HTTP. So I'd have to create a "micro HTTP server" that runs on the loopback interface and listens for HTTP requests from the GUI, parses them, runs the necessary Git action, then sends the results back to the GUI.

Sort of ugly.

My bigger concern is also for a shared machine; how do I secure the HTTP server so only the git-gui process that is supposed to be using it is able to access it? I guess I could create a 600 ~/.gitguicookie file or some such entity and throw random data into it to initialize it. That's basically all xauth is doing.

Actually I might revisit this XUL concept using an HTTP server and AJAX. I could actually link the damn HTTP server against libgit.a (Junio will hate me). If the server dies XUL can notice it and simply restart it. But there's a whole suite of actions that I can run through the internal APIs with high chances of success, and a lot quicker than forking the corresponding plumbing process, especially on fork challenged machines like Windows.

-- 
Shawn.