Yes, sorry I didn't phrase my post very well: there is a URL for the image, of course, but I was trying to emphasise that there isn't a URL to an image cached on the server's filesystem to pass back, as I don't want to *permanently* cache the image (or implement a cleverer algorithm - there's no need). I simply want the cached image (or intermediates) to be temporary; the user's session seems the obvious candidate for this type of storage to me.
--rob On 7/25/07, Klaus Hartl <[EMAIL PROTECTED]> wrote:
Rob Desbois wrote: > Traunic > > > how does raw image data get you anything? Seems you want the data and > > the image URL via XHR and then dynamically insert your DOM bits (img > > tag w/ URL from response with some sort of wrapper containing your > > legend)... I mean, what you are talking about is technically doable > > (not in all browsers) http://www.kryogenix.org/days/2003/10/18/embedding > > but I am not sure it gets you anything. > > No, you haven't read my post carefully enough. I don't want the image's > URL because the image *doesn't have* a URL - it's generated by a > server-side script. This cannot be. If you want to load the raw image data via Ajax, there *must* be a URL. But this URL could as well be used as src for the image given that the server-side script sets the proper mime type. --Klaus
-- Rob Desbois Eml: [EMAIL PROTECTED] Tel: 01452 760631 Mob: 07946 705987 "There's a whale there's a whale there's a whale fish" he cried, and the whale was in full view. ...Then ooh welcome. Ahhh. Ooh mug welcome.
