[development] SQLite and Drupal 7 -- let's try this again

[Chris Johnson]

It's a very interesting idea, as Robert said.

Can you explain a bit further how the code is improved, and maybe a
couple things which are enabled, by this idea?  Which larger problem
is being solved by this solution -- that is, where is the code really
troublesome right now in handlers and implementing pluggable
subsystems?

..chris

On Tue, Feb 3, 2009 at 10:44 PM, Karoly Negyesi <karoly at negyesi.net> wrote:

> Here we go. The big win is NOT performance. The big win is nice code. I forgot to mention this, silly me. So the problem is that currently we have a fairly ugly way to allow pluggable subsystems and they are not really flexible. You can pick one cache subsystem, that's it. We are planning something called handlers which will let you pick cache subsystems by the table for example. For this, we will change the cache implementations to become a class. However, if we want -- and yes, we want -- to serve cached pages without touching MySQL then we need to somehow specify the pathes to the cache and session implementation. If we have the registry available immediately then autoload just works.