by Zorro » September 13th, 2013, 3:12 am
In this case, the developer has setup some code that:
1. Loads original image into a cache directory or into system memory on the server.
2. Dynamically adds a watermark to the original image.
3. Sends new watermarked image to browser.
4. Deletes new watermarked image from cache directory (keeping the original) or flushes it from system memory.
This is quite simple actually and is very similar to dynamic thumbnail image generators. Thumbnail generators will generate a thumbnail of a specified image based upon some pixel size parameters passed in the URL and then store the thumbnail in a cache directory; it's cached so the server doesn't waste CPU resources re-sizing the original image each time that particular thumbnail size is requested.
Research shows that one in three Clinton supporters are just as stupid as the other two.