The problem with different sessions not working is usually down to the boneheaded approach to authentication used by most sites. It's perfectly possible to support accessing multiple accounts simultaneously, it's just that it's harder work than setting a cookie on "/".
-Dom
Re:Tip for auto-validating PHP generated XHTML
on
Web Standards Solutions
·
· Score: 2, Informative
Actually, it won't be valid, it'll be well-formed. Which is still a good goal.
But you can go further get validity if you want. Instead of putting that stored content into PHP.XPath, try writing it to a temp file and running onsgmls -wxml -E0 -s -c/etc/sgml/catalog $tmpfile 2>&1 over it. You'll need to ensure that you have nsgmls and the W3C DTD's installed, but that's exceedingly simple in debian; you just need the opensp and w3c-dtd-xhtml packages. Any output from that you can stuff into the page somehow. In Perl, I just do $page =~ s/<head>/<head>$err/;.
That's good advice, but why should a developer have to care in the first place? It sounds like the linker has some serious deficiencies if it's not performing all these steps already to me.
I'm always hearing that Perl is obfuscated. But compared to the verbosity of Java, it's delightful. It's like comparing a well written newspaper article with court proceedings.
Actually, neither is fast enough. Particularly where it matters: terminal windows. I've tried gnome-terminal, and I've tried konsole. They're both slow and buggy. xterm may not be as flashy, but it's fast and it works.
Yes, MaxClients in the apachge configuration. See who much RAM you have in the box, see how much each apache process is taking up, divide the one by the other to get a rough figure for maxclients. Tune until you don't swap any more.
Having less processes is not really a problem. Newer connections will just be accepted by the kernel and apache will pick them up when it's ready. As to mod_perl taking up more memory, that's expected behaviour. I've got 25Mb mod_perl processes, but no problems because I've set MaxClients quite low (much lower than the default of 150!).
This sort of thing is well documented in most of the mod_perl literature. Tell you what, why don't you purchase the reviewed book and find out!
Hmmm, you must be smoking something good. Whilst there are some things you can't do under mod_perl (realtime perhaps), MVC is not one of them. In fact, you have an enourmous amount of choice when it comes to mod_perl and MVC - mason, Apache::Template, PageKit, AxKit and so on. There are many other tools to help you with MVC, or you can roll your own if you've sufficient hubris to think that none of the existing stuff does its job.
Please try to research your rants a little better.
The trouble with perl -MCPAN is not only that it won't let you uninstall easily (as somebody else pointed out) but also that it won't let you install a specific version.
I'd really like to have a bundle file list version numbers so that when I install the bundle it doesn't fetch the latest version of everything on the planet. Yes, I know it's documented as doing this. But check the source. It's not implemented. EVery time you use a bundle file, you get the latest version of everything which is not always what you want.
Whilst I agree that Imake isn't the prettiest thing in the world, autoconf/automake/libtool is a hell of a lot worse. At least with imake, you know that the result is just going to be a Makefile, rather than some bastard offspring of sh/m4/make/perl all rolled into one.
Don't underrate the cisco UI. It's one of the best command line experiences out there. No matter what point you're at, press "?" and you'll be told your options. Based on twenex, I believe.
The only thing that's even remotely comparable is zsh.
Perl has excellent unicode support. Yes, it wasn't 100% in perl 5.6, but the 5.8 release is incredibly useful. We've done xml sites with hundreds of megs of articles and the unicode absolutely had to be right. Perl didn't let us down once.
Like your example of Java (although plan-9 did it first), Perl supports Unicode in its core. Strings are natively unicode and regex matches and all string operations are done on a character basis, not byte, by default. You can lexically switch into byte oriented mode if you need to though.
Funnily enough, but the reason that I prefer perl over most mainstream languages (barring Python) is the fact that it's by far easier to read and understand what the code is doing. Larry Wall's background in linguistics has payed off handsomely.
Of course, there's a lot of bad perl out there. There's a lot of bad C, C++, and Java too. Yes, yes, I know you don't write any, but that doesn't mean that it's not there.
Slashdot Mirror
-Dom
-Dom
But you can go further get validity if you want. Instead of putting that stored content into PHP.XPath, try writing it to a temp file and running onsgmls -wxml -E0 -s -c /etc/sgml/catalog $tmpfile 2>&1 over it. You'll need to ensure that you have nsgmls and the W3C DTD's installed, but that's exceedingly simple in debian; you just need the opensp and w3c-dtd-xhtml packages. Any output from that you can stuff into the page somehow. In Perl, I just do $page =~ s/<head>/<head>$err/;.
-Dom
That's good advice, but why should a developer have to care in the first place? It sounds like the linker has some serious deficiencies if it's not performing all these steps already to me.
-Dom
-Dom
-Dom
-Dom
-Dom
-Dom
-Dom
Having less processes is not really a problem. Newer connections will just be accepted by the kernel and apache will pick them up when it's ready. As to mod_perl taking up more memory, that's expected behaviour. I've got 25Mb mod_perl processes, but no problems because I've set MaxClients quite low (much lower than the default of 150!).
This sort of thing is well documented in most of the mod_perl literature. Tell you what, why don't you purchase the reviewed book and find out!
-Dom
-Dom
Hmmm, you must be smoking something good. Whilst there are some things you can't do under mod_perl (realtime perhaps), MVC is not one of them. In fact, you have an enourmous amount of choice when it comes to mod_perl and MVC - mason, Apache::Template, PageKit, AxKit and so on. There are many other tools to help you with MVC, or you can roll your own if you've sufficient hubris to think that none of the existing stuff does its job.
Please try to research your rants a little better.
-Dom
I'd really like to have a bundle file list version numbers so that when I install the bundle it doesn't fetch the latest version of everything on the planet. Yes, I know it's documented as doing this. But check the source. It's not implemented. EVery time you use a bundle file, you get the latest version of everything which is not always what you want.
-Dom
-Dom
From your local neighbourhood fortune cookie file.
-Dom
-Dom
The only thing that's even remotely comparable is zsh.
-Dom
-Dom
-Dom
-Dom
-Dom
-Dom
Of course, there's a lot of bad perl out there. There's a lot of bad C, C++, and Java too. Yes, yes, I know you don't write any, but that doesn't mean that it's not there.
-Dom
Thank $DEITY for kilograms, a sensible unit.
-Dom (an anti-imperial uk denizen)