NNTP-Posting-Date: Tue, 11 Mar 2014 12:00:24 -0500 Date: Tue, 11 Mar 2014 17:00:20 +0000 From: lipska the kat Organization: Trollbusters 3 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 Newsgroups: comp.lang.java.programmer Subject: Re: What Application Server are you using? References: <3843209b-7a1d-4812-a8dc-06738ed60658@googlegroups.com> In-Reply-To: <3843209b-7a1d-4812-a8dc-06738ed60658@googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Message-ID: Lines: 34 X-Usenet-Provider: http://www.giganews.com X-AuthenticatedUsername: NoAuthUser X-Trace: sv3-Oyq7TIKpjVEs2uve0YP16iWeu9eMNCIVlrF3cXsWlA59qQuOH6UCTQq47hyyvWgVi1sOnRP8MT/mWro!TJGNczGcKXJVkVw5vgE/1Om2WwB6W/tnF+kX0FudLnJeyHNhNflZv57OZX/7JKZhqrKzI5wXXkM= X-Complaints-To: abuse@btinternet.com X-DMCA-Complaints-To: abuse@btinternet.com X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 3466 Path: csiph.com!usenet.pasdenom.info!news.stben.net!border3.nntp.ams.giganews.com!backlog3.nntp.ams.giganews.com!Xl.tags.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!local2.nntp.ams.giganews.com!nntp.bt.com!news.bt.com.POSTED!not-for-mail Xref: csiph.com comp.lang.java.programmer:27728 On 11/03/14 15:54, Robert Hutchings wrote: > Please forgive my ignorance, but I thought Apache Tomcat was specifically designed as a "servlet engine" for JSP. Is that correct or incorrect? :) > Java Server Pages compile to Servlets, I suppose it's really correct to describe Tomcat as a 'Servlet Engine', or 'Servlet Container' but it's more than that, it's a pukka web server as well. When I started to use Tomcat it was mostly used as a Servlet Engine behind an Apache httpd front end ... and many people still use it that way. However over the years the performance has improved so much that personally I can do without the overhead of configuring Apache and focus instead on configuring Tomcat. My Tomcat servers listen on port 80 just like Apache httpd and serve static content as well as dynamic. I have the container managed data sources configured and access them via a JNDI lookup just like the heavyweight servers. The kind of things I can't do OOTB are host entity/stateful/stateless session beans or host remote interfaces via RMI-IIOP. There is no built in messaging or support for distributed transactions(last time I looked), however given that most of these things were designed to provide scalability and given that memory is now so cheap and server performance is now so good I see little point in the added complexity of an application server. Servlets and jsps are all part of J2EE or whatever it's called now so I suppose you *could* call Tomcat a lightweight app server. I mostly do smaller business applications now, a few hundred visitors a day no more than 1000 concurrent sessions but otherwise a full blown database backed business application and I have never had any problems with performance. I guess it depends on what you intend to do and how you see the application scaling in the future. -- Lipska the KatŠ: Troll hunter, sandbox destroyer, treacherous feline and farscape dreamer of Aeryn Sun GNU/Linux user #560883 - http://www.linuxcounter.net