Edward <ed**************@yahoo.com> wrote:
How so? I have been able to open images in browsers using this markup.
I found some good examples at:
http://delegate.org/delegate/sample/data-url.html.
Forget this page immediately.
The second example of this page (with the "/-/" prepended to the data
url) will result in the following:
The relative URL "/-/data:image/gif;base64,<data>" will be resolved
to "http://delegate.org/-/data:image/gif;base64,<data>" and then will be
send back to the server. The server now translates the "<data>" into a
GIF image and sends this image back to the browser which it can display.
In the first example (the real "data:" URL scheme) will result in the
following:
The URL "data:image/gif;base64,<data>" will be directly translated into
a GIF image by the browser and so can be directly displayed.
The differences is:
The second example needs more than the double amout of data that is send
to and from the server. And it is working only with the help
of the server, and only if the server is able to translate such
URLs. That means there must be a certain script installed on your server
in order to use this special URLs. And because of the doubled data
transmission you'll better use the ordinary way to embed images
It doesn't make any sense to prepend "/-/" to "data:" URLs.
--
Alexander