Sounds like he wants to weigh in on all his options more than being 'afraid' to do something. For instance I can't use mod_perl for a lot of my projects because the administrators of the servers the projects run on don't want it, so that's a consideration when picking modules, I have to pick ones that will run fairly fast even in a CGI environment, not because I don't love mod_perl but because it isn't always availiable.

Maybe I didn't make myself particularly clear, but I never said I was 'afraid' of using OO Perl, mod_perl and definately not unknown modules, because I do that all the time! I'm module crazy! :-) I simply thought that I should consider all options before just going ahead with what I know.

The only way to 'evolve' my perl skills is to experiment and dabble in technologies and try to understand them. However I also dont want to use technologies for the sake of it when a simple solution will do

ps. dont call me chicken! :-)

Let's see, you wrote:

I was thinking about Mason, the trouble is I havent really done any work with it before,

which to me indicates you find it troublesome to work with a module you haven't used before. Furthermore, you write:

doesnt it require mod_perl?

this indicates to me usage of mod_perl is something don't fancy doing. Finally,

Also the thought of OO Perl is a little worrying

what does "worrying" mean in your language?

dont call me chicken

All I can see of you is what you write here. If you don't want to be called chicken, don't act like one!

Abigail

ooooo, i'm not acting like a chicken, just being prudent about my choice of technology and approach!

Grrrrr!!!!!!!!!!!