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! :^)

• Re: Can we help? by dmalloc on Friday 20/Jul/2001, @16:46

  well dqwit is working on DAV integration into the http io slave, so the DAV part is covered. Knowing (because I use it) that apache has an excellent mod_dav there would be no nreal need to integrate it directly into zope as long as the data that will be m odified can be ins ome for accessed in it hard coded form by apache. I do not know if zope uses a databse. anyways WebDAV is in thw works, because I wanted to offer writing an io slave for it and dawit said he was on it

  [ Reply To This | View ]

• Re: Can we help? by Paul Everitt on Sunday 22/Jul/2001, @13:16

  First, could you give me the email address for dqwit? I want to find out, and beg if necessary, if he's doing the part of WebDAV that retrieves the document source. Next, to cover your subsequent points...Zope already supports DAV. Basically, Zope runs as a process outside of Apache. Zope includes protocol handlers for HTTP, FTP, xml-rpc, FastCGI, etc. You can put Apache in front of Zope and use mod_proxy as the RPC. Yes, Zope uses a database, it's internal object database written in Python. More info at: 1) http://www.zope.org/Documentation/Articles/ZODB1 2) http://www.zope.org/Documentation/Articles/ZODB2 The database is organized like a filesystem, rather than relationally. This makes it a great fit for DAV. Objects in the database are instances of Python classes, meaning there are real first class "document", "image", "folder", and user-defined classes for DAV to tinker with. Here's the HTML "GUI" for working in the object database, http://www.zope.org/Members/michel/ZB/UsingZope.dtml#2-1 We've been doing DAV for two years now and thus I have a huge desire for a good DAV client environment. Having a better DAV client in KDE would be a big win. Do you use Python much?

  [ Reply To This | View ]

• Re: Can we help? by APW on Monday 23/Jul/2001, @00:12

  Dawit Alemayehu <adawit@kde.org> Google Search: http://www.google.com/search?client=googlet&q=dawit%20KDE

  [ Reply To This | View ]