Jesse Erlbaum wrote:
Hi Richard --
I can't help you with that error, but out of curiosity: Why did you
choose ::FileDelegate?
Perhaps a more pointed version of the same question: Why did you choose
to use ::FileDeletegate instead of a more fully thought-out server page
system like Mason?
-Jesse-
Jesse, I think the simple answer is that CGI::Application was my first
foray into managing runmodes in a better manner than I had previously
used - huge numbers of if-elsif-else blocks. It was suggested to me that
C::A was a fairly thin abstraction layer over 'standard' web app
development and that I should not find the learning curve too steep.
I have found that to be good advice, and have now invested so much
time/effort into getting CGI::Application to work with my current
web-apps under development - and am happy to have done so - that I don't
feel inclined to abandon my efforts and start again elsewhere. My
current 2 apps at least *will* see the light of day as CGI::Application
apps!
I quite like the idea of splitting the application into one file per
runmode - not least so I could ditch the requirement to use
Apache2::Reload when developing under mod_perl - though I realise
FileDelegate is not the only way to do that. But it's probably the
easiest way I know - using a C::A plugin.
If I could get Catalyst installed in my Win32 development system I would
take a look at that, but only in the sense of exploring the next stage
of development for me - and with no expectation at this stage that I
would like it any better than CGI::Application. As for Mason - well
maybe sometime in the future?
Best regards,
--
Richard Jones
Leeds, UK
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
