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=21769>. 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=21769 Multiple actions for a request ------- Additional Comments From [EMAIL PROTECTED] 2003-07-22 06:25 ------- As you will find when you try this in real life, there are significant gotchas to the notion of executing multiple paths through the request processing lifecycle for a single request. My personal opinion is that implementing an approach like this would allow people to confuse the (MVC) controller role with that of the model. The best practice in such a circumstance is to have the single action that is invoked in response to a particular request delegate to the series of business logic functions needed to set things up for the subsequent response. That speaks to a need for mechanisms to compose the execution of multiple business functions. It's a real need. Trying to corrupt a "front controller" design pattern into supporting this is the wrong answer to the problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
