Hi folks, nevermind; I figured out a way to make it work without this change :)
The basic hooks for a stampede protection will be checked in later; I hope I will be able to provide a sample implementation soon.
Cheers, David On 15.01.2009, at 15:27, David Zülke wrote:
Hi everyone,(this message has been CCed to the users mailing list and BCCed to some people directly; please direct feedback to the *Agavi Dev Mailing List* if you can, and to me directly if you must)I'm currently implementing support for a so-called Stampede Protection mechanism in Agavi (http://trac.agavi.org/ticket/744).The problem is that it is next to impossible to implement properly, due to the fact that a View's initialize() method can change an Output Type, I cannot know what caches to lock or extend when preparing the Action run.Already, Agavi's ExecutionFilter implementation is quite a bit of a mess, because it needs to deal with a related situation (Action cache exists, but View cache doesn't), and "go back" several steps in this case and start over.We could simplify the current code enormously by simply mandating that the Output Type must not be changed once the Action has started running. That way, the chicken-and-egg-situation would be remedied, and a stampede protection mechanismI'd like to stress that this is currently one of the options being considered. There are other possibilites we're still investigating. I do, however, believe that this (radical) approach would properly solve the problem and have long-term benefits in terms of maintainability of the framework.I'd like to hear *your* thoughts on this now, and in particular, I'd like to know if you're currently using this functionality at all, and if yes, if it would be problematic for you to move this to the routing or to a filter, and why.Also, if you have any kind of questions about the entire situation, including even the smallest technical details of the stampede protection etc, please don't hesitate to ask.Now... Feedback plz, from everybody, kthx! :) Cheerio, David
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Agavi Dev Mailing List [email protected] http://lists.agavi.org/mailman/listinfo/dev
