On 15/10/2010 08:02, Mladen Turk wrote: > Hi, > > I'm working for quite some time on the light-weight > VFS layer (with the java.io.* as the only provider at > the moment) to be used as the Tomcat's physical file > system access. The ultimate goal is to be able to run > the Tomcat on top of things like Hadoop or similar distributed > file systems (eg. GFS) by just using the provider module.
Sounds interesting. What is the use case? Resilience? How far does just a DirContext implementation get you? > Now, the amount of changes is pretty huge but it involves > mostly changing the java.io.* with the o.a.t.vfs.* > counterparts. "huge" makers me nervous but it if is mostly search and replace that is less of a concern. Any feeling at the moment to the amount of overhead this adds? > Since this "Pseudo VFS" has exactly the same API > (with the Java7 additions), no functional code change is needed. > Sure there are some additional config directives used > to define which parts are using which vfs provider as default. > (or by just using the > root="file://web/apps" or hdfs://<host>:<port>/web/apps > notion for non-clustered environments) > > I'd like to create a sandbox project for that > (was thinking of /sandbox/tomcat-vfs) +1. If there are any re-factorings that would make this easier then we should look at the feasibility of putting them in trunk. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
