I'm trying to build a WebDAV front-end for several projects so users can
do things like edit database content directly. I haven't found a whole
lot in the mailing archives - it looks like there's some interest but no
serious development going. Is anyone working on something I've missed?
Please correct me if I'm wrong on this:
Currently way to handle DAV requests in PHP because the PHP module
declines the OPTIONs method and you can't get the raw body of the
request, so you can't parse requests by hand.
There are two obvious possibilities:
1) Modify the apache sapi to accept the OPTIONS method and provide
a function to extract the raw request body so that the various requests
can be parsed within PHP.
2) Use a lightweight webdav server (e.g. one of the Python or Perl
implementations) to proxy for PHP so that in-bound requests are POSTed
to a PHP script.
Only #1 seems to be usable for much beyond proof-of-concept work and
it's still a kludge, even if the gory parts are sensibly wrapped in an
object.
I think there has to be an easier way of doing this that I'm missing.
Any suggestions?
Chris
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
