I think we have here an issue with maintainer (Steve) taking up too much on himself. Cache Router idea was great, but it turned out to be too much of job to maintain all engines in the same way.
I suggest to make cache engines pluggable, and move them to different projects, then make a call to other developers who want to maintain them. This will give us all following consequences:

  • Amount of work needed to maintain main package will be greatly reduced
  • It will become clear which engines are not supported, have bugs, or just work. Engine bugs won't put blame on main package
  • Hopefully reduced amount of work to support engines will result in better quality of main package

Also it will be possible to develop own engines without bugging Cache Router developer.
Hope this helps.

Comments

slantview’s picture

slantview commented

well this is pretty much going to happen in Drupal 7, so I wouldn't worry about it too much.

andypost’s picture

andypost
he/him
Primary language Russian
commented

@slantview do you have a plans to review a critical issues? There's a lot of well-tested patches but it seems like you ignore them...

andypost’s picture

andypost
he/him
Primary language Russian
commented
Status: Active » Closed (won't fix)

Now we are joining forces to maintain this!

I see no reason to split this module into thiner pieces.... and there's a lot of modules like apc, memcache already