One of the features (depends how you look at it) is, at the time of adding new albums and photos to your albums, all photos are stored in a secured central repository. None of the original photos is touched or EXIF tampered with. Instead, at runtime, the FStop Image Handler, services the photos on demand. And, once a photo for a photo type is serviced, it is stoerd in a file cache system. From that point on, the photos are directly pulled from the cache. One can always clear the cache and regen the serviced photos.

Since the engine is fully config and db driven, most of the rendering is handled by raw controls by overriding the ::Render() behavior. This includes for HTMLWriter based features for simple things such as Meta tags, Title, etc. The admin component of F/Stop is fairly easy to use, you create an album, add photos to it (either one at a time or bulk upload), edit properties of albums and photos and the engine handles all of the plumbing. 

Few other features include text-to-image-watermark, rounded edges on images, icon doc dhtml behavior, etc.  If you're interested in trying the engine out in your own server, please ping me at:

caio
Nagi