Ohh, I'm not kidding about this. I kid about other things, but not this. :^)

Here's what I'm talking...first and foremost, have it do WebDAV as well as it does FTP. If you want to be wacky, have it support locking/unlocking and DAV property viewing/changing.

If you want to see what this would look like, take a look at three products for Windows that do this: WebDrive, WebIFS and TeamDrive. All three are let you map a drive letter to a DAV folder.

This is a pretty simple extension to HTTP. Zope (and other dynamic systems) also need an option to be implemented that no other DAV client has yet to do, which is to retrieve the *source* of a page rather than the rendered GET of the page. The DAV spec anticipates this.

Let's see, the DAV spec requires digest authentication to be used instead of basic authentication in cases where SSL isn't used. I don't know if the existing HTTP support in KDE can do digest auth.

GnomeVFS implements DAV, but for some reason that mystifies me, they don't provide any ability to do authentication. I don't know why someone would want a read-write web with no authentication.

There's good functionality beyond the above, but it wouldn't be the domain of the kio_slave.

So, there you have it -- I wasn't kidding! :^)