- To monolith-ize or not?
It's a matter of taste, but I personnally like the (usual) idea of several scripts using common libraries.
(database access, presentation, system interaction...)
By the way I see no additional difficulty on managing cookie/session via several scripts instead of one.
(did I miss something?)
- To XML-ize or not?
By making a clear distinction between the data and the presentation, XML is a "must have" nowadays,
furthermore a lot of emerging technologies use it as input/output format or at least as a pivot format.
One advantage I grant to XML over standard templating system, is that XML will provides you more tools
(parser, checker, transformer...) than any templating system.
It would be cool to use DTD to validate (for a particular browser) HTML code
produced via XSLT translation from XML...
The question is much "how to do it ?"
The article gives an interesting way, axkit may be a good option too,
anyway I'm sure some people here will probably give you the best advices on XML.
- (not quite as perl-ish) MySQL or Postgres?
Postgres! if your goal is to do the things the right way.
Even if (beccause?) I've been using MySQL for 2 years at the office,
I'd recomment MySQL only when speed is REALLY needed
Foreign keys, trigger, views... make the DBA life so easier.
"Only Bad Coders Code Badly In Perl" (OBC2BIP)