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

[Pavan Kumar Sunkara <pavan.sss1991@gmail.com>]

On Sat, Apr 17, 2010 at 11:57 AM, Tatsuhiko Miyagawa
<miyagawa@bulknews.net> wrote:
>
> Sam Vilain <sam <at> vilain.net> writes:
>
> > > of CGI.pm, perhaps also using one of URI dispatchers[5][6].  Plack/PSGI
> > > looks like the future of Perl web scripting... but is currently quite new,
> > > at version 0.9930.
>
> I admit that it's quite new - not old anyway, but don't get fooled by its
> version number. It's already adapted by almost all perl frameworks and
> used by lots of companies on production.
>
> > Ok so PSGI is the port of Python's WSGI to Perl.  Plack is the reference
> > implementation, and also quite heavy at 2.5MB tarball.
>
> No, the tarball just contains 2.4MB of .jpeg file for large-file download
> and upload testing. Its  dependencies are kept minimal - only requires
> LWP, URI and some pure perl modules.
>
> > required.  Dancer however seems to stand out at only 94kB tarball, minimal
> > non-core dependencies and support for PSGI.  The HTTP::Server::Simple::PSGI
> > dependency should let it support the 'instaweb' case with pure perl.
>
> You can already use CGI::Emulate::PSGI (via Plack::App::CGIBin) to run
> gitweb.cgi on Plack, or whatever web server that supports PSGI - like
> HTTP::Server::Simple::PSGI you just mentioned.
> http://gist.github.com/346068
>
> > It should be possible for the script to figure out what filesystem path it
> > is being run from, perhaps find a local lib/ dir and then add that to @INC.
> > In shell scripts you just use FindBin, I don't know whether that is still
> > expected to work from eg mod_perl but there's bound to be a solution for
> > that.  So yeah I'd say just aim to ship lots of .pm files in a nearby dir
> > alongside the script...
>
> Or use App::FatPacker.
>
> --
> Tatsuhiko Miyagawa
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

We need to keep gitweb dependancies as less as possible. So, using
frameworks will be a bad idea, as everybody might don't want to use
them.

Coming to splitting of gitweb, as Jakub said installing a split web
script would be a problem, but we can have a solution the problem by
using proper algorithms. First, we parse the URL and get to know which
function to be implemented and then we include the necessary file and
call the function which will then execute and return the proper HTML
output.

This way, we can no longer worry about installing the split webscript.
All we need is to install the basic gitweb.pl file which does all this
basic parsing and calling other perl files. The other files just
needed to be in the path.

-pavan