StorageService API

[Cantor, Scott]

Needless to say, I think the question of whether to leverage object persistence in the project is a major one, and I'm not trying to hijack it. But I don't think we have a lot of time to make it *unless* we can live with my suggested approach of wrapping a BLOB-based API with a PersistenceManager<T> like thing, and just sticking a String-based object serializer inside that wrapper.

So perhaps the big thing to work on is the objection to BLOB storage and understanding why that will be a problem (given that I haven't seen it be a problem in the RDBMS case). After that, it's really just an API discussion, and APIs can be wrapped.

I can see LDAP being a case where it's a problem, for example, so maybe that's the core issue. To date, we have not tried to supply an LDAP back-end for the use cases we have for our storage APIs.

But to flip it around, one of the reasons for sticking with BLOB is that something like a cookie certainly can't hande anything else.
 
-- Scott