Re: [PATCH] gitweb: don't use pathinfo for global actions

From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date: Jan 7, 2009, 21:32 UTC
Message-ID: <cb7bb73a0901071332x1c07114cp2eefbc4490db1eb0@mail.gmail.com>
In-Reply-To: <200901061837.23637.jnareb@gmail.com>

On Tue, Jan 6, 2009 at 6:37 PM, Jakub Narebski <jnareb@gmail.com> wrote:

Show 16 quoted lines

> On Fri, 2 Jan 2009, Giuseppe Bilotta wrote:
>> Accepting global actions in use_pathinfo is not a very robust solution
>> due to possible present and future conflicts between project names and
>> global actions, therefore we just refuse to create PATH_INFO URLs when
>> the project is not defined.
>
> I think it is quite robust solution and it makes sense; we use
> shortcuts http://git.example.com for projects_list page, and
> http://git.example.com/path/to/repo.git for overview 'summary'
> action for a project, therefore pathinfo has to look like the
> following: http://git.example.com/repo/action/hash with "action"
> _after_ "project".  And there is also matter of backward compatibility
> of URL (URLs shouldn't break).
>
> Anyway, we have $home_link for default project_list page, which
> is path_info without project, and query without query string...

Today I had this idea: a possible way to have global actions into the path would be to use an invalid project name, but I'm not sure if there ARE invalid project names at all. Maybe using something very abstruse such as _projects_ (underscore "projects" underscore) or even just _ (underscore).

The only thing I can think of for which global actions in path WOULD be interesting would be that project tag paths would become something like http://git.example.com/_/tag/sometagname which can be tagged by the rel-tag microformat http://microformats.org/wiki/rel-tag ...

-- 
Giuseppe "Oblomov" Bilotta