Apache and Tomcat and Apache Tomcat What is the relationship and the difference

What is the relationship with the Apache Tomcat and the difference

Transfer: https: //www.cnblogs.com/zangdalei/p/8057325.html

 

Apache  and  Tomcat  are web server network, both both connections and differences, HTML, PHP, JSP, Perl, etc. during the development process, the need to accurately grasp their own characteristics, to select the best server configuration.

　　Apache is the web server (static resolution, such as HTML), tomcat is a java application server (dynamic resolution, such as JSP)

　　Tomcat is just a servlet (jsp also translated into a servlet) container, can be considered an extension of the apache, but can run independently of the apache

Both from the following points can be compared:

　　1, both of which are developed by apache

　　2, both HTTP service functions

　　3, both of which are open source free

contact

　　. 1) is a common Apache server itself only supports ordinary web html i.e., plug-ins can be supported by php, may also be communicated (Apache Tomcat unidirectional connections, that is accessible with the Apache Tomcat Tomcat resources, not vice versa).　　

　　2) Apache only supports static pages, dynamic pages but like Jsp Tomcat will need to deal with.

　　3) Apache Tomcat integration and use:

　　　　If the client requests a static page, you only need Apache server responds to the request;

　　　　If the client requests a dynamic page, it is the Tomcat server responds to the request will be resolved JSP and other web analytic code back to the Apache server, and then returned to the browser via Apache.

　　　　This is because the server-side jsp is interpreted code, Tomcat only dynamic code analysis, Apache return the parsed static code, Apache + Tomcat integration so that you can reduce service costs Tomcat.

　　4) Apache and Tomcat are independent and can be integrated on the same server.

the difference

　　Apache is the C language, supports a variety of features and modules in order to extend the core functionality; Tomcat is written in Java, better support for Servlet and JSP.

　　1, Apache Web server, Web server delivers (serves) page so that the browser can browse, Web server dedicated to handling HTTP requests (request), but the application server is to provide (serves) the business logic (business through many protocols for the application logic).

　　Apache Tomcat is running on the application server, the application server provides the client application can call (call) the method (methods). It's just a servlet (jsp also translated into a servlet) container, Apache can be considered an extension, but can run independently of the apache.

　　2, Apache server is a common, ordinary itself only supports static html pages. But you can support via plug-in PHP, you can also communicate with the Tomcat (one-way Apache Tomcat connection, means you can access resources through Apache Tomcat, not vice versa), Tomcat is jsp / servlet container, which also supports HTML, JSP, ASP, PHP, CGI, etc., which require some manual debugging CGI, but very easy.

　　3, Apache focused on the http server, Tomcat servlet engine focused on, if run in standalone mode, functionally equivalent Tomcat and apache support JSP, but not ideal for static pages.

　　4, Apache can run without rebooting the year, stability is very good, but is not necessarily Tomcat.

　　5, the preferred web server is Apache, but Apache can not be resolved jsp, servlet only by tomcat.

　　6, Apache is the beginning of the page resolution service, developed after the tomcat is, essentially tomcat functionality can replace Apache, but Apache tomcat, after all, is the senior-class people, and the market there are many people still with Apache, so Apache will continue to exist, will not be replaced, apache java can not resolve things, but fast parse html speed.

Both examples:

　　Apache is a car, can be installed on top of something, such as html, etc., but can not hold water, it must be filled with water to a container (bucket), and this may not be placed on the bucket truck, the bucket that is TOMCAT.

Both integration:

　　Apache is a web server environment program, he can use as a web-enabled server but only supports static pages, dynamic pages, such as the asp, jsp, php, cgi

　　If you are running under Apache jsp environment you need an interpreter to execute jsp page, and this is the Tomcat jsp interpreter

　　So why JDK it? Since then jsp need to connect to the database will provide jdk drive-way connection to the database, so you want to run jsp web server platform you need APACHE + TOMCAT + JDK

Integration benefits:

　　If the client requests a static page, you only need Apache server responds to the request

　　If the client requests a dynamic page, the Tomcat server is responding to requests

　　Because the server-side jsp interpreted code, so that integration can reduce service costs of Tomcat

 

Apache  and  Tomcat  are web server network, both both connections and differences, HTML, PHP, JSP, Perl, etc. during the development process, the need to accurately grasp their own characteristics, to select the best server configuration.

　　Apache is the web server (static resolution, such as HTML), tomcat is a java application server (dynamic resolution, such as JSP)

　　Tomcat is just a servlet (jsp also translated into a servlet) container, can be considered an extension of the apache, but can run independently of the apache

Both from the following points can be compared:

　　1, both of which are developed by apache

　　2, both HTTP service functions

　　3, both of which are open source free

contact

　　. 1) is a common Apache server itself only supports ordinary web html i.e., plug-ins can be supported by php, may also be communicated (Apache Tomcat unidirectional connections, that is accessible with the Apache Tomcat Tomcat resources, not vice versa).　　

　　2) Apache only supports static pages, dynamic pages but like Jsp Tomcat will need to deal with.

　　3) Apache Tomcat integration and use:

　　　　If the client requests a static page, you only need Apache server responds to the request;

　　　　If the client requests a dynamic page, it is the Tomcat server responds to the request will be resolved JSP and other web analytic code back to the Apache server, and then returned to the browser via Apache.

　　　　This is because the server-side jsp is interpreted code, Tomcat only dynamic code analysis, Apache return the parsed static code, Apache + Tomcat integration so that you can reduce service costs Tomcat.

　　4) Apache and Tomcat are independent and can be integrated on the same server.

the difference

　　Apache is the C language, supports a variety of features and modules in order to extend the core functionality; Tomcat is written in Java, better support for Servlet and JSP.

　　1, Apache Web server, Web server delivers (serves) page so that the browser can browse, Web server dedicated to handling HTTP requests (request), but the application server is to provide (serves) the business logic (business through many protocols for the application logic).

　　Apache Tomcat is running on the application server, the application server provides the client application can call (call) the method (methods). It's just a servlet (jsp also translated into a servlet) container, Apache can be considered an extension, but can run independently of the apache.

　　2, Apache server is a common, ordinary itself only supports static html pages. But you can support via plug-in PHP, you can also communicate with the Tomcat (one-way Apache Tomcat connection, means you can access resources through Apache Tomcat, not vice versa), Tomcat is jsp / servlet container, which also supports HTML, JSP, ASP, PHP, CGI, etc., which require some manual debugging CGI, but very easy.

　　3, Apache focused on the http server, Tomcat servlet engine focused on, if run in standalone mode, functionally equivalent Tomcat and apache support JSP, but not ideal for static pages.

　　4, Apache can run without rebooting the year, stability is very good, but is not necessarily Tomcat.

　　5, the preferred web server is Apache, but Apache can not be resolved jsp, servlet only by tomcat.

　　6, Apache is the beginning of the page resolution service, developed after the tomcat is, essentially tomcat functionality can replace Apache, but Apache tomcat, after all, is the senior-class people, and the market there are many people still with Apache, so Apache will continue to exist, will not be replaced, apache java can not resolve things, but fast parse html speed.

Both examples:

　　Apache is a car, can be installed on top of something, such as html, etc., but can not hold water, it must be filled with water to a container (bucket), and this may not be placed on the bucket truck, the bucket that is TOMCAT.

Both integration:

　　Apache is a web server environment program, he can use as a web-enabled server but only supports static pages, dynamic pages, such as the asp, jsp, php, cgi

　　If you are running under Apache jsp environment you need an interpreter to execute jsp page, and this is the Tomcat jsp interpreter

　　So why JDK it? Since then jsp need to connect to the database will provide jdk drive-way connection to the database, so you want to run jsp web server platform you need APACHE + TOMCAT + JDK

Integration benefits:

　　If the client requests a static page, you only need Apache server responds to the request

　　If the client requests a dynamic page, the Tomcat server is responding to requests

　　Because the server-side jsp interpreted code, so that integration can reduce service costs of Tomcat