VFS and HTTP based protocols
Submitted by Wednesday, 29 September, 2004 - 06:13
on
Hi,
I have recently done some work on the DAV plugin.
One of the issues that came up was the use of VFS for http based protocols.
If I register my protocol as http, then jEdit tries to use my plugin to access
any files with a http URL. Of course http urls could be stored on a standard
Web server or on a webdav server or on a soap server etc etc etc.
To get around this, I registered my protocol as webdav. The plugin converts this to http
when it acceses the server. (In jEdit, I specify webdav://myhost/mycollection).
However, this causes its own problems. If I download an XML file from the Weddav server
and this file references a style sheet or schema with a http url, jEdit cannot download
these referenced files. If I modify the references to webdav URLs that stuffs up other
software.
It appears to me the the VFS interface is not flexible enough to handle http based protocols.
Is there any way around this?
I have recently done some work on the DAV plugin.
One of the issues that came up was the use of VFS for http based protocols.
If I register my protocol as http, then jEdit tries to use my plugin to access
any files with a http URL. Of course http urls could be stored on a standard
Web server or on a webdav server or on a soap server etc etc etc.
To get around this, I registered my protocol as webdav. The plugin converts this to http
when it acceses the server. (In jEdit, I specify webdav://myhost/mycollection).
However, this causes its own problems. If I download an XML file from the Weddav server
and this file references a style sheet or schema with a http url, jEdit cannot download
these referenced files. If I modify the references to webdav URLs that stuffs up other
software.
It appears to me the the VFS interface is not flexible enough to handle http based protocols.
Is there any way around this?