Yep - that's why I mentioned that as the "favorable" solution hehe - I guess I should have clearified. Whereas you've probably (had the joy of having) implemented this, I just read about it. Hey, by the way, Craig - have you followed my struggle at all? How would _you_ suggest I implement http/https and redirects back and forth under Tomcat + Apache + mod_jk? I'd love a tip or two =) I trust your word a great deal.
Thanks, Eddie Craig R. McClanahan wrote: > >On Wed, 10 Jul 2002, Eddie Bush wrote: > >>You peaked my interest. I did some digging. I see no mention of doing >>load-balancing that does not include Apache. There are other ways: >> >>DNS Load Balancing (affinity not guaranteed - dead server = bad requests) >>Clustering (better - but SSL geeks affinity) >> >>As it happens, you can wire a hardware SSL-decoder in front of your >>cluster-manager and overcome the shortcomings of that approach. I think >>the best solution is Apache + Tomcat though. It's undoubtedly >>cheaper/easier. So - you ready to install Apache yet? Breeze over to >>the Oreilly site and look for "Apache Wrangler" and something called >>LAMP. You'll find an article that will point you to a script that will >>download/install Apache + SSL (it even "pre-configures" it for you - >>whatever that means). If you have the option of using RPMs, I'd go with >>that option though. RPM == good (IMHO). >> >One thing you will need to ensure is that your load balancing solution >routes all requests for the same session back to the same Tomcat instance >(like the balancing through Apache does). > >>HTH, >> >>Eddie >> > >Craig > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
