Re: GSoC 2010: "Integrated Web Client for git" proposal

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 19, 2010, 07:23 UTC
Message-ID: <7vfx2rsy6y.fsf@alter.siamese.dyndns.org>
In-Reply-To: <vpqeiicey0d.fsf@bauges.imag.fr>

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

Show 6 quoted lines

> Pavan Kumar Sunkara <pavan.sss1991@gmail.com> writes:
>
>> Session management reduces the length of URL
>
> ... but OTOH, GET parameters allow painlessly cut-and-paste-able URLs,
> which is in my opinion a must-have for gitweb.

These self-contained URL are used in bookmarks and e-mails to the mailing list. I think "the length of URL" is a red herring at best, and shortened URL that is not self-contained is not an advantage at all.

On the other hand, a proposal about giving multiple clients access to their own individual server-side checkouts (ala "workspace" in DELTA-V) would require some mechanism to maintain the state on the server end, and session management would be one ingredient necessary to achieve that.

When I heard that somebody wants to do a "write support" in gitweb, I naturally thought the proposal was about implementing RFC3253 using git as a backend. I think it would be a reasonable thing to do (as opposed to coming up with an ad-hoc "write support" mechanism that is not compatible with anybody else), but on the other hand it might be a bit too ambitious for a one-student summer project.