> > why overload your administration task (think of backups!) by storing
> objects that won't change? Consider also the extra overhead in the
> cache and across the network in possibly retrieving large blobs that
> your users normally would need to have at the client only on request,
> e.g. via a Show/Select image button.
>
> For the sake of consistency, for example. Keeping files in FS and
> references in DB in synch is a nightmare.
> Overhead level depends only on radius of curvature of application
> coder's hands.
>
> SY, SD.

and just how the files can be supplied in a multi-user environment, stored
on the server in shares? yuk! is another piece of the puzzle.
on-the-fly zip filters is something I need to do sometime.
Alan