[
Lists Home |
Date Index |
Thread Index
]
On Wed, Jul 24, 2002 at 08:29:04AM -0500, Andrew Dubinsky wrote:
>A fully resolved link would include the data within the same file
>resource. E.g. a copy of the resource.
>
><img src="<<binhex data of gif>>" />
>
>I understand that copying the gif data within each file is fat and
>'violates' the spirit of the URI concept. However, in our use, we must
>have the data bound directly to a digitally signed file. In the normal
>use of links, the underlying content of the link could be changed
>without modifying the hashed value of the document.
>
>In a sample use imagine the following xhtml page the end user sees
>within a browser:
>
>Your interest rate is:
><img src="http:://www.scamco.com/images/ratex.gif">
>
><The browser displays a gif of the image for 5%>
I think that you should check whether your browser supports the data: URL
scheme. If it does, use that. It will be fat, of course, but this is the
preferred way to do what you seem to be doing. Whether anyone supports it
is anyone's guess. I'd try it, but I'd have to find the spec, encode an
image, and build a page to test, and, well ... you have a little more reason
to investigate, right? *laugh*
Amy!
--
Amelia A. Lewis amyzing@talsever.com alicorn@mindspring.com
I have spent nights with matches and knives, leaning over ledges, only
two flights up. Cutting my heart, burning my soul. Nothing left to
hold. Nothing left, but blood and fire.
-- Indigo Girls
|
