>
> Well, I haven't used Embperl but I've read the docs a bit and I have some
> idea of how it works.
>
> One big difference that I would point out is that despite its name
> HTML::Mason, is _much_ less HTML centric than Embperl. It is a bit
> mod_perl centric but there is literally nothing HTML specific about it at
> all. We've been talking recently about how to expand mason so that it can
> be used in any sort of context where you have a request (from STDIN,
> email, whatever) for content that you want filled by components.
While you are talking, Embperl can already do this for over 3 years :-)
> From
> what I can tell, this is unlikely to be possible (or desirable?) with
> Embperl.
>
> This means that learning Mason for your website could let you leverage
> this knowledge into creating a generic server, a command line filtering
> command set, or whatever.
>
As Jason already pointed out Embperl has a lot of features for HTML, but you
can use it for all sorts of textfiles. Embperl is highly configurable, if
you don't need/like a specific feature for a given problem, you can just
disable it. The idea of Embperl was to make life easy and to let Embperl
handle as much things as possible for you, but in some sitaution this don't
let you do the things like you want to do them, then you simply disable the
feature.
>From my point of view Mason is much more web (site) centric then Embperl
(this doesn't mean you can't use it outside a webserver)
When Mason came up it's great plus was it componenet model. Embperl has
learned a lot from Mason (and as Jonathan told me when we meet in summer on
the Perl conference, also Mason learnt form Embperl :-) and now Embperl has
also a component model which is as powerfull as the Mason one. The only
piece that is really missing, is the output cacheing of sub components (but
this is only a matter of time).
I think both Mason and Embperl (and Apache::ASP of course) are very
powerfull and it's mainly a matter of style what you prefer.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
