tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David White <dw11...@onemail.at>
Subject Re: PATCH: fix for asset service (branch-3-0 2005-03-16)
Date Mon, 21 Mar 2005 15:11:09 GMT
On Mon, 2005-03-21 at 10:00 -0500, Howard Lewis Ship wrote:
> Another solution is to change the asset service to reject all incoming
> requests if externalization of assets is enabled.  In this scenario,
> assets are copies out of JAR files onto the file system (mapped to a
> web folder).  Currently, the asset service continues to execute.  By
> disabling it, you close the gap ... and have an effective whitelist
> because files are extenalized when a URL referencing them is generated
> (as part of a page render).

That seems quite reasonable, and would work well. The whitelist would
generate itself, and be persistent across server restarts.

> However, this has some issues in a  cluster, unless the file system /
> web folder is shared or shadowed between servers in the cluster.

SAN/NAS's are a cluster's best friend. :)


To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message