I think there has been more than enough discussion around this issue which I did not interfere with nor influence in any way.
However, to let it continue to spin over and over is unproductive. I'd love to hear other solutions other than configurabe cache key strategies or a time-based delay caching strategy, but the time to debate whether this is a defect or not is officially over: it is a defect. Let's find the right technical solution to make fastpath more robust, please. ------Original Message------ From: Don Baccus Sender: AOLserver Discussion To: AOLSERVER@LISTSERV.AOL.COM ReplyTo: AOLserver Discussion Sent: Aug 21, 2008 12:25 PM Subject: Re: [AOLSERVER] Data "corruption" with fastpath caching On Aug 21, 2008, at 8:14 AM, Dossy Shiobara wrote: > > I've remained silent on this issue because I didn't want to be > accused of "stifling the community," etc. ... > End of discussion. Accused. Guilty. ---- Don Baccus http://donb.photo.net http://birdnotes.net http://openacs.org -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- Dossy Shiobara [EMAIL PROTECTED] -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
