On Tue, 2012-10-09 at 22:19 +0100, Mark Thomas wrote:
> If we do go this route I'd like to change the scheme from "jndi://" to
> "tomcat://". This is for several reasons:
> - I believe there was a complaint that "jndi://" clashed with another
> component.
> - It makes clear the old and the new ar
On 09/09/2012 20:13, Mark Thomas wrote:
> This is issue e) in Konstantin's comments in TOMCAT-NEXT.txt
> I think this boils down to "Is there a requirement for a scheme that
> provides unified URLs?" While it does hide the details of where stuff is
> from an application, if does so with a layer
This is issue e) in Konstantin's comments in TOMCAT-NEXT.txt
Copying Konstantin's notes:
Goodies:
- Uniform URL space. Both files and directories can be represented,
hiding details of aliases, resource jars, etc.
- It hides implementation details.
- Permissions can be e
