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