On 3/06/2003 8:57 Carsten Ziegeler wrote:
My point is, sending every three days an email to the list, saying "there are too many open patches/bugs" doesn't really help or motivate.
Exactly. When I read these mails, I always end up with this vision of people trying to 'corporatize' open source projects, in the genuine belief injecting such corporate project artefacts will help. Other than OSS projects 'owned' by a single company (which Cocoon luckily is not), I don't think this approach works out.
If people need food for discussion, here's my utterly uninformed and out-of-the-head opinion on these patches:
=======================================================================
6879 [PATCH] Cache improvement using ESI invalidation protocol
-> one man show - and too specialized towards a certain specific goal
I agree, but as a newcomer haven't wanted to mark things WONTFIX because hey, someone else MIGHTFIX! There are some technical problems with the ESI solution IMVHO - it requires the back end system to know what urls are associate with each record in the database.
I'm working on a similar capability though for externally invalidated cache items. I'm not far enough in, but what I'm looking at could provide hooks for an updated version of this ESI scheme as an alternative to JMS (which I see as a better solution) as a means for contacting cocoon about the external events.
If someone with more "authority" wants to mark it WONTFIX go ahead but if not, I can.
Geoff
