[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 102265] nested kioslaves for archives
From: Thiago Macieira <thiago () kde ! org>
Date: 2005-04-01 11:01:08
Message-ID: 20050401110108.1483.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=102265
------- Additional Comments From thiago kde org 2005-04-01 13:01 -------
> I ran the URIs through QUrl
Well, you can't do that. They are URIs, not URLs. Only the first one is supposed to \
be a URL and should validate against all. That indicates a problem in QUrl somewhere.
> First, 'multi:' itself is an implementation detail that shouldn't be visible
> to the user, who is only interested in where the data is, not how to glue
> components for accessing it together.
The idea is that Konqueror creates those automatically. If you click a zip file in \
file://home/me, it'll automatically generate the URL \
multi:///?p1=file,/home/me/file.zip&p2=zip,/
The user will see a mess in the Location, but it'll work. Hence the idea of a cleaner \
URI for KDE4.
> Therefore, it permits things like these:
>
> multi:file:///home/me/file.zip,http://host
> multi:gzip:,zip:/file
We would enforce that only the first protocol is allowed a \
username-password-hostname-port part. That is, everything after the first one has \
just the first slash.
As for the second option you gave, that would be an error because no file was given.
> I would like to throw the pipe syntax I had mentioned earlier back into the
> mix:
>
> file:///home/me/file.zip|zip/file.tar.gz|gzip|tar/file.tar.bz2|bzip2|tar/file.txt
The big problem here is that that's a URL and we can't change its meaning. That URL \
means file "file.zip|zip/file.tar.gz|gzip|tar/file.tar.bz2|bzip2|tar/file.txt" in \
/home/me on your local filesystem. That can't be changed.
We could add in a multi: prefix, which would allow us to change the meaning of the \
special characters. But in that case, we would stumble upon what I had proposed as \
URI, only with pipes instead of commas.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic