Forum OpenACS Development: How to store images?
What is "best practice" for storing and retrieving images?
If I look at dotLRN (header image) and OpenACS (user-portrait) I should conclude that the Content Repository is the way to go. However, this creates 2 objects per image and rows in 5 tables (I believe).
I plan to display these images, together, in another 'custom' object.
As I was reading Gratuitous use of acs_objects? I started to wonder whether storing images this way is the right way to go .
What is "best practice"? What gives "best performance"? Any suggestions?
On the other hand, if you have the CR store them in the DB your DB backups will contain all the images making restoring from scratch a simpler process. But returning them to users will be somewhat more expensive, particularly in the PG version.
As regards the expense of the CR I would say that while many have argued that it must be expensive to use none have proven that either the object system or the CR is truly a bottleneck on any live system.
The permissions system is a bottleneck, that we know, but that's due to its implementation and has nothing whatsoever to do with either objects or the CR.
Nice to see you around here again... (Keith is my work supervisor at USU )
Did you mean to say that your experience has taught to keep the number of objects down (instead of not to keep it down)?
I know several things were fixed in 4.5 with respect to the permissions system (although I can't remember exactly what), and more things were improved in 4.6 (see http://www.brasileiro.net/roberto/artigos/new-changelog.html specially the acs-kernel and acs-tcl sections).