From Resin 3.0
An overview of the features and capabilities in Resin and Resin Professional.
Resin is provided in two versions, Resin Professional and Resin Open Source. Resin Professional adds features and enhancements commonly needed in a production environment. Resin Open Source is suitable for hobbyists, developers, and low traffic websites that do not need the performance and reliability enhancements of Resin Professional.
Resin Professional provides a number of reliability features, including automatic server restart, detection and restart of locked or stalled servers, and monitoring of JVM memory usage for applications with memory leaks.
- See also: Clustering
Clustering provides the ability for multiple servers to appear as one server to clients. Clustering provides enhanced reliability and allows sites to scale up as server demand increases,
Clustering is supported with the standalone web server, Apache, and IIS.
Persistent and distributed sessions
- See also: Distributed session
Persistent sessions guarantee that a server can restore the contents of the HttpSession object when it is restarted. Distributed sessions provide the ability for multiple servers in a cluster to share the values stored in the HttpSession.
Performance enhancing native code
- See also: JNI
Resin Professional includes a native code libary on both Windows and Unix platforms. Native code is used to provide significant performance benefits in areas like socket connections, keepalive connections, and file system access.
- See also: OpenSSL
Resin Professional uses native code to link to the OpenSSL libraries, a much better and more efficient SSL solution than the Java facilities provided by JSSE.
HTTP proxy caching
Resin Professional provides a memory and disk based caching system for increased performance benefits. Server caching can speed dynamic pages to near-static speeds. Small but frequently accessed resources such as images and css files are cached in memory and served directly to the client, avoiding even a read from the disk.
Many pages require expensive operations like database queries but change infrequently. Resin can cache the results and serve them like static pages. Resin's caching will work for any servlet, including JSP and XTP pages.
- See also: GzipFilter
Bandwidth costs are significant for many websites. The GzipFilter enables automatic compression of responses for browsers that support it. Use of the GzipFilter reduces bandwidth usage and may provide significant cost savings.
Resin is tested and supported on the following operating systems:
- Mac OS X
Resin is known to work on the following operating systems:
Resin is used on these operating systems, however there may or may not be difficulties with Apache integration, and the JNI code that Resin uses to increase performance may not be available.
- See also: Resin web server
Resin includes a fast and flexible HTTP server. Many users find that the performance, flexibility, and features of Resin make Resin a desirable replacement for Apache or IIS. Resin, for example, serves static content as fast or faster than Apache.
Hypertext Transfer Protocol (HTTP)
Secure Socket Layer (SSL) 3.0
- See also: SSL
Apache 1.3 and 2.0 integration
- See also: Apache
IIS 5 and IIS 6 integration
- See also: IIS
- See also: Quercus
Resin includes a 100% Java implementation of the PHP language and libraries that runs in interpreted and compiled mode.
- See also: Database
Resin provides a robust connection pool for any JDBC 1, JDBC 2, or JDBC 3 database driver.
- See also: Virtual host
Resin supports virtual hosts with little overhead and provides mechanisms for addition and deledtion of vrtual hosts with restarting the server.
Java Servlet 2.4
Java Server Pages (JSP) 2.0
Java Server Pages Standard Template Library (JSTL) 1.0
- See also: jstl
- Reference: [http:/www.jcp.org/en/jsr/detail?id=052 JSTL 1.0 specification (JSR-052)]
- See also: Amber
- Reference: JSR 220
Java Connector Architecture (JCA) 1.5
Java Management Extensions (JMX) 1.2
J2EE Deployment API (JSR 88) 1.0
- See also: CGIServlet
Java Transaction API (JTA) 1.0.1b
Java Transaction Service (JTS) 1.0
Java Message Service (JMS) 1.1
Enterprise Java Beans (EJB) 2.1
Enterprise Java Beans (EJB) 3.0
The J2EE specification requires that containers support CORBA. Although Resin supports CORBA, Caucho does not recommend the use of CORBA.