This is my scenario. I've got 18 different webapps, mapping to hundreds of apache vhosts, each with its own security needs and varying services. We've got literally years of development tied up in the automated config generation system.
Resin is a great appserver. Trying to replace Apache though is like trying to replace a dump truck with an SUV. Sure both can be used to carry stuff around, but they aren't really meant for the same things. Frederick R. Cooper Director of Information Technology The FeedRoom "The leader in live and on-demand enterprise online video solutions." P: 646.613.7860 M: 917.673.4559 F: 212.925.6471 -----Original Message----- From: resin-interest-boun...@caucho.com [mailto:resin-interest-boun...@caucho.com] On Behalf Of Joseph Dane Sent: Tuesday, March 10, 2009 2:30 PM To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Why Apache? On Mar 10, 2009, at 7:14 AM, Aaron Freeman wrote: > Why use Apache at all? you may have a situation where you haven't got a single webapp, but many webapps and other creatures living under a single host. in that case apache makes a nice top-level dispatcher, proxying requests to the various PHP, CGI, j2ee webapps, static content, and other assorted junk. -- joe _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
