Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I always thought that the argument Rasmus made about PHP being scalable because it didn't share anything by default was kind of silly. I mean, you could say the same thing about bash-scripting. (Or Perl, of course.) To make an interesting multi-page web application, you have to introduce some kind of state, usually via sessions of some kind. The mechanisms for saving and restoring state aren't fundamentally different for Java than they are for PHP: cookies, a database, etc.
    • If you commit to saving and restoring state, then the options are pretty much the same.

      The difference is when you start persisting state in memory, share it across threads, and expect it to always be there by design. That's when you start to see scalability problems: session affinity becomes a requirement, max users per server, max concurrent connections per server, hunting and killing long running processes, etc.

      That's the kind of resource management that gets you in trouble, and makes you move toward sha
      • None of the Java servlet implementations I used stored state in memory. Maybe that was done really early on, or is an option on some of them. It's certainly not the norm.