If we were to implement DAV support, then it would make
excellent sense to put the PMCMS source files (mhtml) on
the server too.
RFC2518 describes the distinction between source and
output documents (as for CGI-scripts) (source property).
In the DAV-spec, this is mentioned in connection with
dynamic content. While that's useful enough, I wish to
have the DAV client (PMCMS) generate the output document,
but I do not think that there is any problem in DAV by
uploading a document with a source attribute.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=191604
http://www.webdav.org/cadaver/ is a command line DAV
client.
If we were to implement DAV support, then it would make
excellent sense to put the PMCMS source files (mhtml) on
the server too.
RFC2518 describes the distinction between source and
output documents (as for CGI-scripts) (source property).
In the DAV-spec, this is mentioned in connection with
dynamic content. While that's useful enough, I wish to
have the DAV client (PMCMS) generate the output document,
but I do not think that there is any problem in DAV by
uploading a document with a source attribute.