Just one point for clarification:
if we use Content-Disposition: inline; uri="http://abc.com/hithere.html"
then
1) the contents of the uri parameter cannot use "encoded words" for any
characters
greater than 127--a basic mime limitation. Instead the encoding method
described in
RFC1738 would have to be used.
2) I am still a bit confused on how to "fold" this parameters. I guess
that the uri
parameter can be folded on any deliminter such as "/.:", any others ?
Content-Disposition: inline
uri="http://abc.com/root/
src/hithere2.html"
Note that URLs can get very long and folding will be necessary.
However, if we use a new header like "Content-Location:" or "Content-URL:"
or
"Content-BaseURL:" then RFC1522 encoding could be used.
____________________________
Mark K. Joseph
Advanced Applications Center
The Wollongong Group. Inc.
(408) - 469 -1854
mailto:izzy(_at_)aac(_dot_)twg(_dot_)com