I've been getting by for a while with my single instance of Apache 1.3 and single instance of Tomcat 4, using WARP to connect them (on Red Hat 7.2). While a bit disorienting for someone so new to all of that, I was able to get everything configured and working about six months ago.
Now that I'm trying to serve multiple servlet-based domains, however, I'm starting to have to dig into the ugly innards of these two beasts, and I'm more than a little bewildered. It's a lot to absorb, when you just want it to work, so you can get back to your primary task: application development. Anyway, I'm getting a lot of conflicting signals regarding WARP versus Jk2. I chose WARP six months ago, because, at the time, it seemed to be the future. Now, however, I'm getting the impression that WARP is being replaced by Coyote JK 2. Given the fact that I've got a lot of reconfiguring to do either way, which is the smart way to go? Smart, in this case, I suppose has more to do with avoiding obsolescence, than with any particular feature such as in-process or load balancing, although those are certainly desirable features. Mostly, though, I just want to get beyond this roadblock and not have to revisit it for a looooong time! :-) Advice, industry observations, and prognostications are welcome. And just in case I sound less than grateful, I think this is an absolutely amazing amount of powerful, free software. I just wish it was documented better. :-) If I had the time... Thank you, Lee Grey Grey Matter ____________________________________________ If you've ever opened more than one browser window at the same time, you need URL in One at http://www.URLinOne.com. There's no software to install, and it's free! -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
