Roberto, I think you're confusing the issue here by saying that vfs could provide webdav support for aolserver. I could be wrong, but a brief skimming of the vfs examples indicates that vfs can act as a webdav client, but it can't act as a webdav server, which is what we really want.
Here are some of the examples I found by following the links that you provided:
vfs::urltype::Mount ftp
file copy ftp://foo.bar.com/pub/Readme .
file copy ftp://user:password@foo.bar.com/private.txt .
or
vfs::urltype::Mount ftp
set image [image create photo -file ftp://ftp.ucsd.edu/pub/alpha/tcl/alphatk/alphatk.gif]
pack [label .b -image $image]
or
vfs::zip::Mount foo.zip foo.zip
cd foo.zip ; glob *
or
vfs::urltype::Mount ftp
set listing [glob -dir ftp://ftp.scriptics.com/pub *]
or
vfs::urltype::Mount http
set fd [open http://sourceforge.net/projects/tcl]
set contents [read $fd] ; close $fd
If you evidence to the contrary, that vfs can act as a webdav server, then I would be interested in seeing it.
Even so, vfs would be nice if we had webdav support in aolserver, because you could then remotely mount the CR on your local file system and directly edit content using your favorite text editor instead of some crappy web interface.
