padik.wordpress.com

Julio M. Merino Vidal says, the Apache HTTP Server is the most popular web server due to its functionality, stability, and maturity. However, this does not make it suitable for all uses: slow machines and embedded systems may have serious problems running it because of its size. Here is where lightweight HTTP servers come into play, as their low-memory footprints deliver decent results without having to swap data back to disk. Similarly, these small HTTP servers are suitable to serve static content efficiently so as to allow Apache, mod_perl, mod_python, or even servlet containers to handle dynamic requests without tying up memory-hungry children to serve small images. In other words, these applications can serve as a complement to your existing full-featured web server, not as a replacement. One of these servers is thttpd, a simple, small, portable, fast, and secure HTTP server. Among its features are support for the HTTP/1.1 standard, CGIs, virtual hosts, and IPv6. Read more.

JavaPractices says, storing SQL as text, outside of compiled code, eases maintenance significantly : 1. It minimizes the ripple effects caused by changes to the database schema. For example, if a table name or column name changes, the fix is usually an easy search and replace in a single text file. 2. For developers new to a project, having SQL all in one place makes it significantly easier to learn the database structure if an older application needs to be migrated to a new framework, then the SQL is readily available for porting to the new application. 3. If necessary, changes to SQL can even be made after deployment, by changing the text file and doing a restart or a refresh. This can occasionally be very useful. For example, if users ask for a change in the sort order of some data, then the developer can very likely implement that change without a redeployment (and maybe even without a restart, if the tools support a refresh). 4. adding support for a new relational database may become simply a matter of translating any non-portable SQL statements. Read more.

Apache Jakarta Project says, this is the top-level entry point of the documentation bundle for the Tomcat 4 Servlet/JSP container. Tomcat 4 implements the Servlet 2.3 and JavaServer Pages 1.2 specifications from Java Software, and includes many additional features that make it a useful platform for developing and deploying web applications and web services. (a) Servlet 2.3 provides Web developers with a simple, consistent mechanism for extending the functionality of a Web server and for accessing existing business systems. A servlet can almost be thought of as an applet that runs on the server side–without a face. Java servlets make many Web applications possible. Servlets are the Java platform technology of choice for extending and enhancing Web servers. Servlets provide a component-based, platform-independent method for building Web-based applications, without the performance limitations of CGI programs. And unlike proprietary server extension mechanisms (such as the Netscape Server API or Apache modules), servlets are server- and platform-independent. This leaves you free to select a “best of breed” strategy for your servers, platforms, and tools. (b) JavaServer Pages 1.2 technology enables Web developers and designers to rapidly develop and easily maintain, information-rich, dynamic Web pages that leverage existing business systems. As part of the Java technology family, JSP technology enables rapid development of Web-based applications that are platform independent. JSP technology separates the user interface from content generation, enabling designers to change the overall page layout without altering the underlying dynamic content. Read more.