We’ve been running our production apps with Jetty since we dumped JBoss about a year and a half ago (or more… I forget). Had a few wrinkles on the way, but nothing jumps immediately to mind as a hair pulling, kick the monitor off the desk type episode. Up until recently we were serving in excess of 2 million page views per day with nary a hiccup.

PS. If you enter your nickname incorrectly, it asks you to correct, but there’s no input box to do so (obviously you can hit the back button to fix the problem though)

You’re trying Tomcat with Apache, eh? That explains much.

I’ve found Tomcat to be relatively easy to install and configure for years. Then again, I’ve never needed to integrate with Apache. Personally, I can’t imagine running a site where Tomcat was the weakest link instead of bandwidth. I think I can explain Tomcat’s popularity, despite any configuration or documentation issues it has: It’s free and open source. If you’re developing for the Internet, you will be constrained by bandwidth costs before you tax Tomcat’s ability to serve more pages. In the worst case, you can always get a bigger box. If you’re developing for an intranet you probably aren’t serving much static content. So, Apache integration is poor, because it isn’t really very important.

I had no trouble installing servlets on the 4.x series, but once Tomcat began to include its graphical frontend, I did run into trouble. For some crazy reason I could not get my servlets loaded, and as a result abandoned upgrading. And you’re right, the documentation is lousy.

As to integrating with Apache, I managed to do it using the older method. (Sorry, but I can’t remember the names of the older and newer modules. It’s been a while.) That documentation was awful! I’m certain that it was written by someone for whom English is not his native language. Don’t get me wrong, my father speaks English as a third language, but he’s not writing documentation for anything. I had hoped the most recent Tomcat would be better, but your experience isn’t encouraging. I’ll have to see for myself. By the way, nice job on the site. I’m all for longer articles. I’m still meaning to get up to the Albany XML Developers meeting the next time you’re speaking.

P.S. — I once imagined that my love of the Whedonverse and my love of programming, XML, etc. would never cross paths, but now that you’ve quoted ‘insane troll logic’, well, clearly my delusion of separation was also insane troll logic. Because, geeks.

Java, XML, and the Whedonverse intersected for me some years ago. See Buffy in Cyberspace from way back in Episode 8.

Several websites have been getting authors and “luminaries” to write articles or blog for them in an aggregated location in order to keep the content flowing. Just curious why you decided not to join the bandwagon and post your articles elsewhere. But, on the other hand, since you’ve come up with your own articles site, how about getting a few pals to write articles for The Cafes as well? Or simply open up submissions to all, and you can pick/choose what to post?

Maybe you can post an updated “Why we need Java 3.0″ article?

A typo you made in “Buffy in Cyberspace” seems almost intentional, “demonstarted”, at least if you hyphenate it as “demon-started” (“Because a recent show really impressed me with a level of cluefulness I hadn’t previously seen demonstarted in Hollywood.”). Bwahahaha! Hmmm, now what does that mean, exactly? The other day I was thinking about Giles’ aborted attempt to have Willow “scan” (no doubt in a rather useless PDF-y form) his entire library of demonology, and about the later appearance of the (apparently) incomplete online searchable database, “Demons, Demons, Demons” (which appeared on Angel the Series even more prominently). And someone said something in her Livejournal that got me to really thinking about it. Of course, I then wrote a long, ranty reply about how the new post-season seven Watcher’s Council should hire “us” on, to mark everything up in XML and throw it all into Philologic or some other search engine to make it all truly useful, quickly searchable, sortable, and grokable. With the advances in OCR — the burned single-edition stuff from “Gingerbread” and the blowing up of the Council in season seven notwithstanding — it would be much more useful and complete than anything currently existing in the ‘verse. Of course, Andrew has probably already undertaken just this task, being the nerd that he is. Although when I start thinking like this, putting myself in the ‘verse as a programmer to help them, I know for sure I am _becoming_ Andrew.

(Of course, my real point was that the old Quentin Travers paternalistic mentality would have precluded any such digital archive, because keeping the knowledge in paper form only [untranslated to boot] keeps that knowledge in the hands of those who understand it, the Watchers, thereby giving them a purpose and maintaining their power. Making the data accessible to the Slayer and the lay-person [Xander] means that the old power structure crumbles, but since it has crumbled anyhow, now our time is at hand! XML will prevent the next apocalypse by saving all that “Leafing Randomly Through Various Tomes Over Donuts and Coffee” time [leaving out that scary amount of time the markup might take to actually DO, haha]. Or there’s the scary Wolfram & Hart data access solution, ick.)

One disadvantage here to the lack of threaded comments is that it leaves open too much room for human error in picking something for the Subject line. Because although one can self-thread visually with a good subject line, most of us are bound to mess up and leave it blank, or type something incorrect there. Just a thought. I hope the site *does* get popular enough that you do have such problems.