Implement a storage subsystem

[david]

Right now, Storage is only used for sessions. That is, of course, lame. We want something general-purpose that can be used in app code, for caching, and so on.

With a storage manager, much like the current database manager.

With chained storages (e.g. read from memcache first, then, on failure, from database, but always write to both), lots of drivers

Of course, we need to maintain BC and therefor some smart way to integrate the "session" storage (AgaviMemcacheStorage ... AgaviMemcacheSessionStorage ... AgaviSessionStorage ... fail!), maybe through moving the session read/write/blah into the user, which then uses a storage or such?

BC could be implemented via the factories.xml config handler, because that new feature would, of course, have http://agavi.org/agavi/1.1/config as the namespace! So for a 1.0 NS, it transparently creates a storage manager with just one session storage, and for 1.1, it requires a <storage_manager> tag be there (that would then need a separate storages.xml). And in the case, AgaviContext::getStorage() returns the session storage as it is now. Only really difficult question seems to be this session storage integration in case multiple implementations exist. Maybe a storage decorator or so? :)

Anyway, sounds like a really good candidate for GSoC!

[david]

see  http://trac.agavi.org/wiki/Cleanup/Storage for new ideas

[david]

in a way, this is related to #748

[david]

mmh, I meant wiki:Cleanup/Storage of course

[david]

While we're at it, we could/should implement support for <parameter>s in <caching>s to allow more fine-grained control of $whatever, at least in custom implementations... that requires that the config is actually passed to the read/write/check methods, though, which is why it wasn't done for 1.0

[david]

(In [3945]) storage manager basics, refs #661

[david]

(In [3946]) committed by accident in [3945], refs #661