We did both. We stored the file in the DB. Then when the file is retrieved
from the db, we write the file to the filesystem. The app would check for
the file on the file system first if not found it gets it from the db and
then writes it to the file system for next time. This has the advantage of
We started using a shared file system so we could easily invalidate the file
cache, but this came later.
-Original Message-
From: Randolph Kahle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 16, 2005 3:28 PM
To: jug-discussion@tucson-jug.org
Subject: Re: [jug-discussion] storing
I like to add this caveat. We arrived at this solution, because somebody was
storing images in the db in the original design, and this was a major
bottleneck. This was a workaround so we did not have to change as much code
yet get the performance we wanted. The workaround had some nice advantages
