Re: CGI::Prototype criticism 1 - cannot use POST-redirect-GET paradigm

Personally I avoid modules with no new versions for more than two years. This not a strict rule - but the perl web-framework field seems to be very competetive recently - so in this case I would rather stick to it.

Comment on Re: CGI::Prototype criticism 1 - cannot use POST-redirect-GET paradigm

Replies are listed 'Best First'.
Re^2: CGI::Prototype criticism 1 - cannot use POST-redirect-GET paradigm by merlyn (Sage) on Dec 19, 2008 at 16:23 UTC
So you're going to downgrade something that is stable, and is being used for commercial sites as we speak, simply because there are no significant outstanding bugs to fix (other than a bit of windows testing patches), and instead opt for things that are either buggy or not complete, and therefore have recent releases? Ok, your choice. But not one I would make. My clients using CGIP are happy. That's all. -- Randal L. Schwartz, Perl hacker	[reply]
Re^3: CGI::Prototype criticism 1 - cannot use POST-redirect-GET paradigm by zby (Vicar) on Dec 19, 2008 at 16:29 UTC
My mistake - I was thinking about choosing a library for new projects - not about continuing old ones. I should have made it clear.	[reply]
Re^3: CGI::Prototype criticism 1 - cannot use POST-redirect-GET paradigm by Anonymous Monk on Dec 19, 2008 at 16:27 UTC
It don't fit!	[reply]