Re: [Resin-interest] Why Apache?
If you have the money, you can alleviate that at another OSI level. Ronan Lucio wrote: there's more than one reason. Serving different sites/services on the same server, not all can be served by resin for various reasons: These are the typical reasons. If you're running a specific Apache module (like mod_perl) or running several different kinds of backends, or prefer the logging, or mod_rewrite works better for you than Resin's rewrite-dispatch, then Apache can be a good choice. I didn't hear anybody talking about mod_evasive. How do you care about DoS attacks? Of course mod_evasive isn't a solution for that, but it helps a little. Helps to identify a suspicious attack when you see one or more IPs sending a huge amount of requests. Ronan ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
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
[Resin-interest] Why Apache?
After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
Apparently they prefer the log output. I'll try to get you more specifics if I can. Scott Ferguson wrote: On Mar 10, 2009, at 10:19 AM, Daniel J. Doughty wrote: Some of my developers prefer how Apache logs activity. Can you give some more details? The Apache /server-status or the log output or something else? Some of that logging might be straightforward to add to Resin. -- Scott Aaron Freeman wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ 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
Re: [Resin-interest] Why Apache?
Hi, Why use Apache at all? there's more than one reason. Serving different sites/services on the same server, not all can be served by resin for various reasons: a) Rewriting Service: mod_rewrite has no real pendent b) Different Servlet-Containers on port 80: There are a couple of services which just wont run under resin (my favorite is TeamCity which runs on a Tomcat instance because of that). c) PHP Not everything's running with resin and there are some projects out there which just need the Apache-PHP plugin d) Different resin-instances on port 80: I don't want my TestEnvironment interfere with Live Services when a restart of the container is necessary. Apache is a nice and powerful software to combine these different aspects all. Best regards, --- Jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
Static file serving, perhaps? I don't know the current benchmarks but Apache has always had the reputation of being very fast for static files, whereas that's not what resin is optimized for. I say this from the POV of not using Apache at all, though: we use resin behind HAProxy for load balancing, and a lighttpd instance for image files. Rachel On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman aaron.free...@layerz.com wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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
Re: [Resin-interest] Why Apache?
I like very mych Resin as app. server. but if we talk about http servers I think apache is more reliable, more documented, more flexible and faster. e.g. LocationMatch \.gif$ Header set Cache-Control post-check=36000,pre-check=99 /LocationMatch Scott Ferguson wrote: On Mar 10, 2009, at 10:19 AM, Daniel J. Doughty wrote: Some of my developers prefer how Apache logs activity. Can you give some more details? The Apache /server-status or the log output or something else? Some of that logging might be straightforward to add to Resin. -- Scott Aaron Freeman wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ 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
Re: [Resin-interest] Why Apache?
I don't agree with part 1 even, with the advent of vmware/xen/virtualbox there is no reason to cram a bunch of stuff on a single server. It makes your infrastructure way less upgradable, reliable, and testable. a) The rewriting in resin is pretty good, its all regex, just like any other rewrite. You may have to learn some new stuff, but that kind of how IT works :) b) You can do this with resin vhosts as well, either ip based or ipless. c) You can also do this with resin :) http://quercus.caucho.com/ d) Same thing, but if you use a virtualization product its a no brainer to clone production instances for QA on the same hardware. I find resin by itself to be faster and easier to manage. The less software you run the easier and safer your site will be. Running apache introduces more code that you need to patch and manage, and apache is not the safest or fastest webserver on the market. Just some food for thought :) On Tue, Mar 10, 2009 at 1:41 PM, Jan Kriesten kries...@mail.footprint.dewrote: Hi, Why use Apache at all? there's more than one reason. Serving different sites/services on the same server, not all can be served by resin for various reasons: a) Rewriting Service: mod_rewrite has no real pendent b) Different Servlet-Containers on port 80: There are a couple of services which just wont run under resin (my favorite is TeamCity which runs on a Tomcat instance because of that). c) PHP Not everything's running with resin and there are some projects out there which just need the Apache-PHP plugin d) Different resin-instances on port 80: I don't want my TestEnvironment interfere with Live Services when a restart of the container is necessary. Apache is a nice and powerful software to combine these different aspects all. Best regards, --- Jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest -- -jk ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
On Mar 10, 2009, at 10:44 AM, Rachel McConnell wrote: Static file serving, perhaps? I don't know the current benchmarks but Apache has always had the reputation of being very fast for static files, whereas that's not what resin is optimized for. I say this from the POV of not using Apache at all, though: we use resin behind HAProxy for load balancing, and a lighttpd instance for image files. Actually, Resin's static file performance matches Apache's, because Apache really isn't all that fast. If you really need ultra fast static files, then something like lighttpd or nginx would be a better choice than Apache. -- Scott Rachel On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman aaron.free...@layerz.com wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
On Tue, Mar 10, 2009 at 12:14:36PM -0500, Aaron Freeman wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? Thanks for asking this Aaron! We're getting a lot of useful feedback. (You tell that you've hit a nerve when so many people respond so quickly... :-)) From the point of view of support, I can say that whenever Apache enters the equation, the complexity goes way up. If there's any way you can avoid using Apache with Resin, I would recommend it. For those who need things like mod_perl or run other application servers, you may have no other choice. Someone else mentioned Apache mod_rewrite, which we have an alternative for in our rewrite dispatch rules: http://caucho.com/resin/doc/rewrite-tags.xtp I find the XML syntax much more readable than the line-noise syntax of mod_rewrite. Emil Emil Ong Chief Evangelist Caucho Technology, Inc. Tel. (858) 456-0300 mailto:e...@caucho.com http://blog.caucho.com/ Caucho: Reliable Open Source -- Resin: application server -- Quercus: PHP in Java -- Java CanDI: contexts and dependency injection ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
I actually love IIS for static content, its very fast and the caching is great. It can beat apache hands down, but not sure on light ot ng. On Tue, Mar 10, 2009 at 1:52 PM, Scott Ferguson f...@caucho.com wrote: On Mar 10, 2009, at 10:44 AM, Rachel McConnell wrote: Static file serving, perhaps? I don't know the current benchmarks but Apache has always had the reputation of being very fast for static files, whereas that's not what resin is optimized for. I say this from the POV of not using Apache at all, though: we use resin behind HAProxy for load balancing, and a lighttpd instance for image files. Actually, Resin's static file performance matches Apache's, because Apache really isn't all that fast. If you really need ultra fast static files, then something like lighttpd or nginx would be a better choice than Apache. -- Scott Rachel On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman aaron.free...@layerz.com wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest -- -jk ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
Hi Scott, Here is my long wait question : How to configure Resin run with nginx? regards Wesley - Original Message - From: Scott Ferguson f...@caucho.com To: General Discussion for the Resin application server resin-interest@caucho.com Sent: Wednesday, March 11, 2009 1:52 AM Subject: Re: [Resin-interest] Why Apache? On Mar 10, 2009, at 10:44 AM, Rachel McConnell wrote: Static file serving, perhaps? I don't know the current benchmarks but Apache has always had the reputation of being very fast for static files, whereas that's not what resin is optimized for. I say this from the POV of not using Apache at all, though: we use resin behind HAProxy for load balancing, and a lighttpd instance for image files. Actually, Resin's static file performance matches Apache's, because Apache really isn't all that fast. If you really need ultra fast static files, then something like lighttpd or nginx would be a better choice than Apache. -- Scott Rachel On Tue, Mar 10, 2009 at 10:14 AM, Aaron Freeman aaron.free...@layerz.com wrote: After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ 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 ___ 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
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
Re: [Resin-interest] Why Apache?
Hi, a) The rewriting in resin is pretty good, its all regex, just like any other rewrite. You may have to learn some new stuff, but that kind of how IT works :) the rewriting in resin has it's limits - at least the last time I tried (I actually wrote to this list to get a replacement in 2007 - and was directed back to mod_rewrite!). mod_rewrite is pretty powerful. b) You can do this with resin vhosts as well, either ip based or ipless. You may have overlooked that I was talking about resin _not_ able to server as a servlet container for TeamCity, so I have to hook in TomCat. c) You can also do this with resin :) http://quercus.caucho.com/ No, you can't. And I don't want to bother about complaints of the 'normal' php-hacker serving low-traffic sites... d) Same thing, but if you use a virtualization product its a no brainer to clone production instances for QA on the same hardware. I don't argue virtualization can be your friend. But handling all more servers doesn't always make your life easier! As long as one server happily fullfills the needs I wont go that road. --- Jan ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Why Apache?
I would dearly love to ditch Apache! The answer for us is our dedicated hoster uses Plesk, so as there are other users/apps on it who use the Plesk PHP panel for their regular admin we have to keep that. After watching a few of these threads about people using mod_caucho with Apache, it dawned on me to ask an open-ended question: Why use Apache at all? I am sure there are good reasons for it out there, so I am just curious what the use-case is for using Apache plus Resin instead of using just Resin? ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.9/1992 - Release Date: 03/09/09 19:20:00 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
