Christopher Schultz wrote:
Er... does that help?
Yes, a lot. It even answers a large part of the question I just posted again. I just don't like your disparaging tone about perl. You know, we perl guys can also "do threads", just as we can also "do OO stuff". We can also "do strict"; we can even do "Singletons" and "closures", so there. The difference is that we can choose to do any of these things or not, depending on how we feel about it, while you Java guys are stuck with one model. ;-) More seriously, apart from being essentially a perl guy, I am also a mod_perl guy, and much of what you so kindly explain has a rather close analogy when thinking about an Apache server and its mod_perl handler modules (which are persistent, unlike cgi-bin scripts). Java and the Servlet Spec are more rigid, in that they enforce a rather strict model, which keeps programmers in line and facilitates collaboration on larger projects. We perl guys just tend to be more on the artistic side, and be able to take liberties with the model. Which does often lead us into trouble when we do not understand what we're playing with. Anyway, many thanks for making the effort to try to explain this in a framework that you thought I would more readily understand. Not everyone is able to do such mental gymnastics, or willing to take the time to do it. Appreciated. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
