Lists Home |
Date Index |
Sorry to reply to myself; how tacky. But there's another tactic, which
may work depending upon the browser (I rather doubt that there are
browsers that support this, but who knows?).
On Wed, 2002-07-24 at 11:24, Amelia A Lewis wrote:
> 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 think that you should check whether your browser supports the data: URL
An alternative is to deliver the entire bundle with content-type:
multipart/related. Look for the MHTML specification. SOAP uses this,
The idea here is that each part has a Content-id: header, and then your
attribute looks like this:
<img src="cid:firstname.lastname@example.org" />
Or whatever the content-id happens to look like. The spec also defines
the content-location header, and describes how to use it (this allows
you to package up a whole page with its inclusions and pass it around as
a bundle, without changing the original references).
However, I doubt that standard browsers-as-delivered are in the habit of
handling multipart/related. But one could try (if they were, then one
could potentially reduce some of the server load, although it would also
be rather unfair to folks who've turned off image loading).
Amelia A. Lewis email@example.com firstname.lastname@example.org
Never imagine yourself not to be otherwise than what it might appear to
others that what you were or might have been was not otherwise than what
you had been would have appeared to them to be otherwise.
-- The Duchess [Lewis Carroll]
This is a digitally signed message part