cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: Proposal: URL Protocols
Date Tue, 30 Jan 2001 17:52:32 GMT
Paul Russell wrote:
> 
> * Berin Loritsch (bloritsch@apache.org) wrote :
> > Paul Russell wrote:
> > > * Berin Loritsch (bloritsch@apache.org) wrote :
> > > > I want to run something by the list regarding the way
> > > > Cocoon uses URLs to get references to files and such.
> > > > This _does_ affect both versions, and it refers to the
> > > > naming of the protocols.  The way Servlet 2.2+ specifies
> > > > to get files from the WAR file is the context.getResource()
> > > > method.  All resources are relative to the context root.
> > > > This is separate and distinct from Classloader Resources.
> > > > My proposal is to specify the following Resource protocols:
> > > > "resource:" This gets a ClassLoader resource, loaded by
> > > >             the Cocoon ClassLoader.  This is what it already
> > > >             does.
> > > > "context:"  This gets a Context resource, pulled by the
> > > >             Context.getResource() method.
> > > Yep. Works for me. +1. How do you propose implementing this? Using the
> > > standard URI api I assume?
> > That would be the long term plan.  The alternative would be to do
> > what is already done in the NetUtils class.  Anyone have experience
> > creating URL Handlers?
> 
> Nope, but I know a little about it. From what I know, I suspect the
> main sticking point is getting Java to use the darned things. There
> are two ways to automatically use them - one is to put them in a
> specific package (um. sun.net.www.url.<protocol>? Can't remember),
> and the other is to set a system property to point at a particular
> package of URL handlers (org.apache.cocoon.url?) and place them in
> there. I'd rather we used the second if that doesn't cause any
> problems elsewhere, because namespace pollution is always a bad thing,
> and I don't remember being a sun employee ;)

Your right.  I'm checking the Manifest specs to see how to specify any
default System parameters so that can happen.

> > The less we have to operate with the filesystem the better.  I would
> > love to see the Jikes people add a JNI interface that would allow
> > use to do just that!  We would get speed and elegance.
> 
> Yeah.
> 
> Are there any compilers out there that have this kind of power? I've
> done a fair bit of compiler theory, and it taught me one thing above all
> else: don't write compilers if you don't have to :)

Unfortunately I don't think so.

Mime
View raw message