I've just made an early Resin 4.0 snapshot available.  Resin 4.0 will  
take over from the 3.2 branch.

It will take a little longer than usual for the next 4.0.0 release for  
two main reasons.  First, there are significant, core changes to the  
configuration and also to the clustering (including distributed  
sessions.)  Second, based on feedback, we want to add any planned  
configuration changes in the 4.0.0 release, rather than updating  
different modules in 4.0.1, 4.0.2, etc.

The 4.0.x tree is tied to the JavaEE 6 specifications, so we won't  
have a final production version until after those specs are completed.

1. Configuration

The main configuration change in 4.0 is the new draft of the Web Beans  
specification, which changed the XML configuration dramatically, and  
allows for a more modular configuration style.  We've started  
migrating appropriate modules to the new style.  The planned modules  
will be: security, rewrite, cluster, remote, and JMS.

For example, the current snapshot includes the security changes.  (The  
old style will still exist for backward compatibility.)  To  
configuration an authenticator, you could write the following:

<web-app xmlns="http://caucho.com/ns/resin";>

   <security:XmlAuthenticator password-digest="none">
     <security:user name="harry" password="quidditch"/>

   <security:BasicLogin realm="hogwarts"/>

   <security:Allow url-pattern="/secure/*">
     <security:IfRole name="student"/>


(Note, the exact syntax is subject to the Web Bean specification,  
which is still in draft.)

2. Clustering

With 4.0, we will enable the addition/removal of dynamic servers to  
help manage load.  The visible changes should be minor, however, the  
internal changes are very large (and a major cause for 4.0.0 taking  

Specifically, the distributed sessions need a changed underlying model  
to properly handle the situation of server creation and removal.  The  
current session backup model assumes the set of servers is fixed.  The  
clustering changes also affect the load balancing, but in a less  
complicated fashion.

The new snapshot includes the session refactoring, but the load  
testing has been minimal.  In other words, the snapshot is suited for  
experimentation only, not for any kind of production.

-- Scott

resin-interest mailing list

Reply via email to