Dave Rolsky wrote:
Uh, both Mason and TT have large active communities, lots of docs, books
about them, code samples.
I agree. There isn't much sense in writing a new toolkit from scratch
when you look at the stuff on this page:
http://perl.apache.org/products/app-server.html
Many of these have
On Tue, 8 Jun 2004 [EMAIL PROTECTED] wrote:
> My 2 cents is that mod_perl lacks an "established" application server/tookits
> so for a serious web application, programmers have to rely mostly on the original
> API to get the full benifit. While there sevearl great application tools like
> mason, e
[EMAIL PROTECTED] wrote:
>
>Occasionally, I thought we might start up with a new application server that
>has features like these: 1) MVC model; 2) XHTML templates; 3) backend
>programming based on XML (e.g. parsing parameters like STRUTS), so other
>java, .NET applications can be translated as ea
It depends how to define "programming language". It seems more properly
a comparison between php and Mason because mod_perl itself is the Apache
API in Perl language. For newbies, this API is indeed hard to program with.
My 2 cents is that mod_perl lacks an "established" application server/tookit
Accidentally only sent this to Perrin.
-
Frank Wiles <[EMAIL PROTECTED]>
http://frank.wiles.org
-
Begin forwarded message:
Date: Tue, 8 Jun 2004 16:53:48 -0500
From: Frank Wiles <[EMAIL PROTECTED]>
To: Perrin Harkins <
