Leon
Thanks for mentioning these items.
By the way, I liked taking in the 360 views.
Maurice
Leon Rosenberg wrote:
Maybe I'm missing the point completely, but why not MD5 encode the
path to your image along with a timestamp, how long this link should
be valid?
I' used this several times, decoding the link in the servlet and
streaming it to the client. You can alternatively have a filter for
url-rewriting. The servlet approach has the advantage of being able to
modify the headers and cache often needed images (not that you would
need it on a good configured linux machine).
check this out as an example:
http://www.stadtplandienst.de/objects/euro360/index.html
for en/decoding look for BlowFishJ (for example).
...
Well all this works, EXCEPT, for the caching part
(which mozilla does know how to do).
You simply can't rely on browser caching behaving. Especially https
caching. Firefox / Galleon cache everything they can get, this is
really ugly, especially if the cache dynamical content with all
headers set (I've seen versions of my site in galleon which were 3
weeks old even after hiting refresh). However, I'm very glad explorer
doesn't cache https, caching https could be pretty critical, or do
you want anyone who has access to you workstation to see your bank
account number ?
regards
Leon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
