DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6879>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6879 [PATCH] Cache improvement using ESI invalidation protocol ------- Additional Comments From [EMAIL PROTECTED] 2002-04-19 16:44 ------- Carsten, all, I've some serious concerns about this patch! I hope I don't offend somebody seriously: (1) It seems like a workaround for an other problem. (2) I don't think it's usefull to add a new core component like the Cache Invaldator Server with a extra background thread, which runs all the time, is used seldom and only for one special problem. (3) Logon to the Cache Invaldator Server, to a internal core Cocoon package seems to be a security issue for me and not well designed. (4) For me it seems like a nice try to bypass some dev. problems in a quick way. When I understand the problem right the dev. above is trying to invalid his generated pages direct in the Cocoon caching system. --> generates a page (from XSP logic) --> checks the ExternalCacheValidity (from XSP logic) --> ExternalCacheValidity requests Cache Invaldator Server (with Logon defined in the cocoon.xconf) --> return true/false if Key valid/invalid I don't understand the problem fully, but the architecture of this solution I don't like. There must be a more elegant solution. So I'm -1 to add this patch! Please correct me if I'm wrong! Greets ~Gerhard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
