#2 Store Items/Channels w/o Serialization

[John Munsch]

Currently items retrieved and the set of channels the
user has subscribed to are stored in files created
using Java object serialization. That has performance
problems and when items or channels change the data
they store, the old items and channels are
incompatible and cannot be reloaded. Avoiding that
annoyance by using a JDBC compatible database (MySQL,
Oracle, Postgres, etc.) to store our items and
channels could avoid both of those problems.

Conveniently, the RSS libraries are written in such a
way that an alternate ItemStore or ChannelStore JDBC
implementation instead of object serialization is an
almost transparent change for most any program that
uses them.

[Don Thorp]

Logged In: YES
user_id=226190

I research HSQLDB and it seems like it will work for what
we are trying to do. Until recently, the limit of a binary
item was ~32K, but they claim to have fixed that bug in the
current release.

[John Munsch]

Logged In: YES
user_id=37658

I'm going to add Prevayler support so the system is crash
proofed without actually removing the serialized
ListItemStore, HashMapItemHistory, and ListChannelStore.
They will continue to be serialized but a crash should not
impact them and exits will occur immediately rather than the
lengthy period they can take now.