I may be gazing at my navel a little too closely, but you used the term "inline-perl approach". Besides CGI, what would be some examples of approaches that are not "inline-perl approaches"?
I am truly seeking the wisest choice of an Apache handler to use for the next 5 years.
Thanks so much for your help! | [reply] |
It's a question of how you organize things. See my templating article for a discussion about the options.
| [reply] |
Besides CGI, what would be some examples of approaches that are not "inline-perl approaches"?
Unless I misunderstood perrin, I think s/he may have just meant that not all templating approaches use Perl for their 'embedded' languages. Template::Toolkit, for example, has its own little language. (I couldn't tell, because I'm not familiar enough with Embperl, whether you're looking for a templating solution or something else, but the suggestion of Mason makes me think that at least what you want to do is within TT's bailiwick.)
| [reply] |
Seriously? Amazon is Mason? The whole thing or just a couple of bits? Wow! | [reply] |
According to the Mason wiki everything (at least as of about a year ago).
And seconded the recommendation for Mason as an alternative. You might also look into Catalyst which I believe supports Mason and TT as view engines (still just starting to look into it myself).
The cake is a lie.
The cake is a lie.
The cake is a lie.
| [reply] |
The front-end web stuff is all Mason.
| [reply] |
I've started reading the O'Reilly book on Mason & wondered about the whole Amazon/Mason thing. So go to http://www.amazon.com/jobs and search for Mason! (Spoiler: it is definitely there!)
| [reply] |
I can confirm that (almost) all frontend amazon is mason. | [reply] |
