Conventional wisdom would dictate writing it for Apache (that's what everyone runs, after all), but I've been working with AOLServer lately, writing a C module for it, and I'd have to say that it provides facilities for developing web applications like Scoop that Apache couldn't hope to touch. Things like a pool of shared database connections and a persistent, global cache are just a few of the really cool features. And it's really fast.

Pretty well too, I thought. But, I will add my thoughts. Scoop is around 20,000 lines of code right now. Probably closer to 23,000 or 24,000. It would be a waste of time to do exactly what scoop did but in java. Scoop has been written by perl hackers for perl hackers, essentially. There are some things (boxes for one, compiled and cached everytime you change them) that I don't know how you would do it in Java.

Someone on k5 said it best when they said if you wanted Scoop in java, you should just write something similar to Scoop, but using Java's strengths to do things Java does well. Don't try to emulate the perlisms. So a Java content management system would be neat. I might even hack on it, I like java. But to copy scoop into java, is a waste of time.

Either way, I think this is just trying to ellicit a reaction, and in regards to that, its been done before and better.