[Andreas]

Hmm, instead of flushing the whole cache (which seems to be a bit too much anyway), what about keeping track of cached keys and only flush those that are really needed?
Eg. when certain data gets cached add the key to an internal list and when a flush is needed flush only those keys that are affected.

That would also avoid authentication problems (which also occur with eAccelerator btw.)