On Thu, 27 Apr 2000, Jason Spisak wrote:
Besides session info, what types of info would be good and bad in a FS storage?
In realistic practical terms anything that involves customer's money is IMO BAD on a home grown FS solution (I'd rather use Oracle or something) OTOH a hit counters (and other type of counters) IMO is better at the FS level. Storing it in an RDBMS implies an extra no_hits_per_day_to_the_web_site going to the RDBMS. Also in many cases it is not that important if some hits are 'lost' in which case you can write very efficient code with minimal locking. With file systems like RaiserFS or XFS it is be possible to have huge amounts of small objects in each directory (and still be efficient) and also provide journaling support (Seems to me they are essentially DBMS). It is possible (but probably difficult to implement) to have a RaiserFS Storage backend to ZODB. A better fit than an RDBMS backend because then you can take advantage of all the powerful FS tools like quota control, selective backups etc etc. Pavlos