Re: More CGIHandler problems

> I take it back, I won't.
>
> Making CGIHandler work like ApacheHandler is just too much code rewriting
> at this point, and would involve lots of API changes.  For example,
> CGIHandler does not divide request handling into making a mason request
> and executing it like AH does.  Instead, it simply calls
> $self->interp->exec which does this all at once.
>
> For 1.40 I definitely want to fix this.  But for now I'd rather just
> release 1.26 with the minimal changes needed to make it rethrow
> exceptions.

Good point, our goal should be to break as little as possible. I've just
added a comment about this in CGIHandler, otherwise someone will
inevitably ask why we didn't try this. I also added a todo item so we
don't forget about it.

In the long term we might want to move CGIHandler out to the MasonX
hierarchy so it can be developed separately. There's no reason it has to be
part of the core, especially if we clean up the Handler concept.

Anyway, I'm ok to release it, but I'd *really* like David W to test it first
if he could. I wanted someone to test 1.25 but no one really stepped up,
then
we had this bug. :)

Jon



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click