NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
It's a different way, not a wrong way :) (Score:2)
Re:It's a different way, not a wrong way :) (Score:1)
It started as a reply to your post, yes. Then I realised it was beside the issue. Anyway, it is why I wouldn’t pick CGIP again.
They’re not, but CGIP scatters the responsibility for dispatch across all of your classes by way of the
respondmethod, and it will not invoke a method other thanrespondin the course of dispatch, nor does it provide a built-in mechanism of passing parameters to it. So you have to rig up the entire machinery to parse the URI and route to the right method invoked with the right parameters, and integrate it with CGIP’s dispatch API.You can do URI-based dispatch in CGIP in spite of CGIP.
Catalyst makes me take a lot of decisions. If that was what I had to do, I would like CGIP. But I didn’t make CGIP do what I want. I wrote everything of interest myself. The presence of CGIP was almost incidental.
In the end I inlined CGIP and trimmed it to the bits I actually used, discarding over ¾ of it in the process. Essentially, I now have an ad hoc, informally-specified, rigid implementation of half of Catalyst, to borrow Greenspun’s turn of phrase.
I’d like a framework that provides infrastructure so I don’t have to.
Reply to This
Parent
Re: (Score:2)