Hi!
I think the use of the ?? would not be a good URI scheme. However, maybe we
could simply make the VFS parameters unique. For example add vfs. in front
of them.
For example,
http://www/path/cgi-bin/send.pl?FILE=ABCTYPE=PDFvfs.proxyHost=proxy.hostvfs.proxyPort=8080
Yes, for sure,
Mario
I think the use of the ?? would not be a good URI scheme. However, maybe we
could simply make the VFS parameters unique. For example add vfs. in front
of them.
For example,
http://www/path/cgi-bin/send.pl?FILE=ABCTYPE=PDFvfs.proxyHost=proxy.hostvfs.proxyPort=8080
or
Hi Mario
I don't quite agree with this - this may be the common case for HTTP,
but the URI spec does not enforce it.
Ok, but how should we differentiate between these both use-cases?
I think we should leave it upto the scheme to decide. So http may decide
to pass it to the server,
Hi!
I think we should leave it upto the scheme to decide. So http may
decide to pass it to the server, while ftp may decide to use it to
talk to the server. i.e. each implementation will know the options
they understand, enforce them and pass any remainder to the server.
How does that
