I was looking for a optimum integration into views for reference/referrers.
While being very happy with the views code, i'm not with cck integration and caching.

I see, if we introduce caching the current way, we need such bidir flushes (cache_clear all on references and referrers).
But as long as we don't have any way to disable this behaviour, it could become very soon a problem in performance.

Think about using node reference from a Article to refer to a Topic Node. Topics can have soon 10'000 articles, where a topic node edit is leading to 10'000s of cache flushes. And that all goes through PHP arrays / memory.

I would most love being able to have views integration without any change to default nodeapi and node caching.
Or we should add some checks to nodeapi if there's a present referrer to start manipulating the cache.
BTW: we might need to flush the cache_content if fields are getting changed... or is it getting flushed automatically by cck on content type edit?

Node references should be very high performance.

What way do you prefer to fix this issue?