Difference between Apache Server and Apache Tomcat

Apache is an HTTP server and Tomcat is a container .
So Apache server can serve the  requests which are static in nature while Tomcat can serve the request which are dynamic. So if the pages are served in JSP/SERVLET then we have to use Tomcat container to interpret them.
Similarly, if you will be using PHP then you need to add its support in Webserver.Webserver is used to just respond to the requests with feature such as load balancing, whereas containers( such as Tomcat) are used to manage the lifecycle of the pages generated using JSP and servlet.


Comments

Post a Comment

Popular posts from this blog

WHY JAVA DOES NOT HAVE POINTERS ................................................................................................................. Well, it's debatable whether Java does or doesn't support pointers.Some would say that everything (well, every reference type) in Java is a pointer -- hence, the ever-familiar NullPointerException. But certainly, these reference types do not give one the sort of direct interaction with memory that we're familiar with from pointers in. Instead, all objects are handled by references, not to be confused with pointers or C++ references. The difference is that Java references do not refer directly to the memory location , but rather contain the pointer to the actual memory location, which the programmer cannot get direct access to. It is also true that pointers are dangerous and lead to memory leaks, memory corruption, invalid memory access, e.g. from uninitialized and improperly initialized variables, indexing out of bounds, a...
Read more

JDBC versus ODBC and other APIs

At this point, Microsoft's ODBC (Open DataBase Connectivity) API is probably the most widely used programming interface for accessing relational databases. It offers the ability to connect to almost all databases on almost all platforms. So why not just use ODBC from Java? The answer is that you  can  use ODBC from Java, but this is best done with the help of JDBC in the form of the JDBC-ODBC Bridge, which we will cover shortly. The question now becomes, "Why do you need JDBC?" There are several answers to this question: ODBC is not appropriate for direct use from Java because it uses a C interface. Calls from Java to native C code have a number of drawbacks in the security, implementation, robustness, and automatic portability of applications. A literal translation of the ODBC C API into a Java API would not be desirable. For example, Java has no pointers, and ODBC makes copious use of them, including the notoriously error-prone generic pointer "void *"...
Read more