I have a fairly large Mason application, and we use subexecs and aborts in a lot of places.
Recently I added profiling code to allow developers to profile code sections wherever they wanted. I also have a default profiling event that starts upon execution of the top-level autohandler, and ends as the last statement in the top-level autohandler; to report total Mason execution time. In some of our flows, when we catch form submission errors, etc., we will basically clear the buffer, call a subexec to return form errors to the user, and then abort immediately. What I noticed is that the the catch-all profile output at the end of the top-level autohandler is still executing, even when we abort from within a subexec. Does aborting within a subexec just put one back into the original parent execution chain? I don't recall seeing that behavior in the documentation; my understanding was that all flow was aborted, period. Am I misunderstanding something? Thanks for any help you can offer. - Jeff BTW, I am running the following: RedHat Linux 7.2 Apache 1.3.28 mod_perl 1.29 HTML::Mason 1.23 (yes, I know it's old, but if it ain't broke ...) ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
