[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 102265] nested kioslaves for archives
From:       Andy Koppe <andy.koppe () ed ! ac ! uk>
Date:       2005-03-24 10:43:02
Message-ID: 20050324104302.26191.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 andy.koppe ed ac uk  2005-03-24 11:42 -------
I accept this isn't a trivial request, but do you agree that nested ioslaves would be \
good for interface consistency and network transparency?

KDE4 is a great opportunity to make these kinds of substantial changes.


regarding 1)

True, these addresses wouldn't be URLs as we know them, but should that be a \
showstopper? KURL could be extended to support nested protocols, whereby standard \
one-protocol URLs would just become a special case.

I don't know what STD3 compliance entails, but I don't think the hostname encoding \
scheme would be a good idea anyway because it's not really human-readable and because \
it wouldn't allow for multiple nesting levels.


Regarding 2)

I don't think that would be a problem from the user's perspective, as long as the \
download is performed transparently, e.g. the user doesn't get to see the temp file \
address, and longer downloads are indicated by a progress bar, which is of course \
what already happens when applications access ioslaves.

But perhaps it's a good time anyway to look at random-access functions in ioslaves \
for protocols that do support it?


[prev in list] [next in list] [prev in thread] [next in thread]