Re: [Gnu-arch-users] multi-committer functionality revisited

[zander]

On Sun, Nov 23, 2003 at 08:30:57AM -0800, Tom Lord wrote:
>     > sftp://address@hidden/path/to/your/archive?umask=XXX
> 
>     > http://address@hidden/path/to/archive?umask=XXX
> 
> Yes, I thought about that, but I do not think it is correct.   In
> fact, for the same reason, I withdraw the suggestion of this syntax:
> 
>     >>        sftp:/%umask=XXX,address@hidden/path/to/your/archive
> 
> and say that only these two are right (with the /// fix):
> 
>     >>        file%umask=XXX:///path/to/your/archive
>     >>        sftp%umask=XXX:/address@hidden/path/to/your/archive
> 
> The reason for this is that the umask parameter modifies the method,
> not the request.  It is a client-side parameter that means, in effect,
> "don't use ordinary {sftp,file} -- use the {sftp,file} transport where
> you set the umask first".

Different layer of abstraction.  It belongs in the part after the colon
because it modifies something chosen after the part before the colon is
parsed.

How many many implementers did it before is that the part before the colon
is the 'name' of the service; and there is only a limited list.
If you want to list your imap mailbox from konqueror you can use the imap:
name, and pass various options to it by altering the url after the colon.

In other works; don't use this way unless you want to invent something
new which can not communicate with anyone else.

-- 
Thomas Zander