to muly(feather), 应该是可行的，不过我一直没有成功 www.caucho.com竹叶上有相关的介绍（版本比较新） 如下：Using Resin as the Load Balancer Resin 2.1 includes a LoadBalanceServlet which will balance requests to backend servers. Because it's implemented as a servlet, this configuration is the most flexible. A site might send all requests for /foo to the backend host 192.168.0.1 and all requests to /bar to the backend host 192.168.0.2. Since Resin has an integrated HTTP proxy cache, the front-end machine can cache results for the backend servers. Using Resin as the load balancing web server, requires a minimum of two configuration files: one for the load balancing server, and one for the backend servers. The front configuration will dispatch several url-patterns to the backend servers, while the backend will need to actually serve the requests. The following example sends all URLs starting with /foo to one of the servers in srun-group a. front.conf <http-server> <host id='front' port='80'/> <srun srun-group='a' host='192.168.0.1' port='6802' srun-index='1'/> <srun srun-group='a' host='192.168.0.2' port='6802' srun-index='2'/> <srun srun-group='b' host='192.168.0.3' port='6802' srun-index='3'/> <servlet> <servlet-name>balance-a</servlet-name> <servlet-class>com.caucho.http.servlet.LoadBalanceServlet</servlet-class> <init-param srun-group='a'/> </servlet> <servlet-mapping url-pattern='/foo/*' servlet-name='balance-a'/> </http-server> The backend server configuration is identical to the server configuration for the hardware load balancer. In general, most sites will use some form of distributed session management. back.conf for all backend servers <http-server> <srun id='a' host='192.168.0.1' port='6802' srun-index='1'/> <srun id='b' host='192.168.0.2' port='6802' srun-index='2'/> <session-config> <tcp-store> </session-config> ... </http-server>
应该是可行的，不过我一直没有成功
www.caucho.com竹叶上有相关的介绍（版本比较新）
如下：Using Resin as the Load Balancer Resin 2.1 includes a LoadBalanceServlet which will balance requests to backend servers. Because it's implemented as a servlet, this configuration is the most flexible. A site might send all requests for /foo to the backend host 192.168.0.1 and all requests to /bar to the backend host 192.168.0.2. Since Resin has an integrated HTTP proxy cache, the front-end machine can cache results for the backend servers. Using Resin as the load balancing web server, requires a minimum of two configuration files: one for the load balancing server, and one for the backend servers. The front configuration will dispatch several url-patterns to the backend servers, while the backend will need to actually serve the requests. The following example sends all URLs starting with /foo to one of the servers in srun-group a. front.conf <http-server>
<host id='front' port='80'/> <srun srun-group='a' host='192.168.0.1' port='6802' srun-index='1'/>
<srun srun-group='a' host='192.168.0.2' port='6802' srun-index='2'/>
<srun srun-group='b' host='192.168.0.3' port='6802' srun-index='3'/> <servlet>
<servlet-name>balance-a</servlet-name>
<servlet-class>com.caucho.http.servlet.LoadBalanceServlet</servlet-class>
<init-param srun-group='a'/>
</servlet> <servlet-mapping url-pattern='/foo/*' servlet-name='balance-a'/>
</http-server>
The backend server configuration is identical to the server configuration for the hardware load balancer. In general, most sites will use some form of distributed session management. back.conf for all backend servers <http-server>
<srun id='a' host='192.168.0.1' port='6802' srun-index='1'/>
<srun id='b' host='192.168.0.2' port='6802' srun-index='2'/> <session-config>
<tcp-store>
</session-config> ...
</http-server>