On Thu, Oct 22, 2009 at 9:10 PM, Howard Lewis Ship <hls...@gmail.com> wrote:
> I would prefer in most cases to provide a simple, public facade around > the internal services, and to provide other hooks that continue to > allow the internals to evolve unhindered by these backwards > compatibility issues. That would be good as well, so the discussion is moved to: "What we could use (or promote) the Resource API for?" More often the ever i tend to look at the Resource API as a solution to "accessing" file around (context or classpath) like configuration one for various libraries, for instance almost all the ChenilleKit supported libraries. Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
