Hey Terrence --
that sounds like a good idea
I didn't mention this in my last message, but I've already written code like
this. Two years ago my company worked on a project for a start-up company
which was developing a Mason-based site. We were hired to develop a login
and security system
On Saturday, January 26, 2002, at 10:14 AM, Jesse Erlbaum wrote:
Hey Terrence --
This is what I used to think, but something very similar to
CGI::Application is coming out for Mason soon, here is a recent
post from the Mason list:
Soon? What kind of FUD is that? CGI::Application exists
On Wednesday, January 23, 2002, at 11:06 PM, Jesse Erlbaum wrote:
Mason is a server-page system. It is, architecturally, no
different from
EmbPerl, ASP, JSP or ColdFusion. CGI::Application is what I
would describe
as an application-oriented architecture. Combined with a templating
Hi Terrence --
I've been meaning to respond to your post. Hopefully I can make this a
meaningful and cogent (albeit late) reply. It's a very complicated topic.
But what is missing from this strap-together approach? What is
better about it? I know for one that constant look-and-feel might
Alright, I am going to put in my 2 cents. Mostly because I am new at this
and think that I have a point of view. Which probably isn't true.
I start doing this 8 months ago. I used regular CGI.pm, then I saw the
write-up on perl.com and decided to give it a go. I had tried Mason, it
did not go
