Weekly todo activity, Dec 28 to Jan 04

Weekly todo activity, Dec 28 to Jan 04

New bug #524: $m->abort and $m->redirect do not propagate out of subrequest
               If a subrequest performs a $m->abort or $m->redirect, it
               does not reach the parent request other than by returning a
               value from $m->subexec (which most people don't check). 

               The current behavior is consistent with requests in general.
               Making $m->abort propagate would make subrequests more like
               component calls in this regard. I'm not sure which behavior
               is more correct. Whatever we do, it needs to be documented. 

               [This is just one of a variety of cases in which we have to
               decide whether subrequests act like requests, or like
               glorified component calls. We need to flush out all these
               cases and document them, even if we don't change the
               behavior.] 

               One solution would be to add a Request parameter (say
               propagate_abort) that causes aborts to be propagated out of
               the request. In the stable branch this would have to be set
               manually in subrequests to avoid backwards incompatibility,
               but in future branches this could be set by default in a
               subrequest. This is cleaner, IMO, than checking
               $m->is_subrequest specifically to determine abort behavior.
Tue Dec 30   Jonathan Swartz created bug
             Jonathan Swartz set version_found to 1.10
             Jonathan Swartz set difficulty to 2
             Jonathan Swartz set severity to Normal
  http://www.masonhq.com/docs/todo/access.html?id=524

New task #525: Make it easier to subclass Component.pm
               It is difficult to integrate a Component.pm subclass that,
               say, adds a single trivial method. Problems: 1) There is no
               way to tell resolvers what component class to create. You
               must create a resolver subclass and override the complex
               get_info() method just to change the component class. 2) The
               most common component type is Component::FileBased.pm, which
               is a subclass of Component.pm. Component::FileBased.pm would
               have to be overriden as well, if only to inherit from the
               new parent. 3) Similarly, subcomponents have a separate
               class, Subcomponent.pm, that would have to be overridden as
               well if you want subcomponents to benefit from your
               addition.
Tue Dec 30   Jonathan Swartz created task
             Jonathan Swartz set difficulty to 3
  http://www.masonhq.com/docs/todo/access.html?id=525




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click