Return-Path: <ovidiu@orion.nsr.hp.com>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 92787 invoked from network); 30 Jan 2001 17:39:55 -0000
Received: from atlrel1.hp.com (156.153.255.210)
  by h31.sny.collab.net with SMTP; 30 Jan 2001 17:39:55 -0000
Received: from orion.nsr.hp.com (orion.nsr.hp.com [15.47.171.122])
	by atlrel1.hp.com (Postfix) with ESMTP
	id 43A318DE; Tue, 30 Jan 2001 12:39:57 -0500 (EST)
Received: (from ovidiu@localhost)
	by orion.nsr.hp.com (8.9.3/8.9.3/client.cv) id JAA03493;
	Tue, 30 Jan 2001 09:39:56 -0800
Message-Id: <200101301739.JAA03493@orion.nsr.hp.com>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0
From: Ovidiu Predescu <ovidiu@cup.hp.com>
To: Berin Loritsch <bloritsch@apache.org>
Cc: cocoon-dev@xml.apache.org
Subject: Re: Proposal: URL Protocols 
In-Reply-To: Your message of "Tue, 30 Jan 2001 11:37:58 EST."
             <3A76EDE6.C7E83013@apache.org>
X-Url: http://www.geocities.com/SiliconValley/Monitor/7464/
X-Image-Url: http://www.geocities.com/SiliconValley/Monitor/7464/ovidiu.tiff
X-Face: 
 ?(@Y~qjBA}~8ZMh5gM4{Q{bE_*:sCJ3@Z?{B*Co=J!#8bb~-z?-0._vJjt~MM59!MjxG%>U
 5>MW^2-\7~z04buszR^=m^U|m66>FdR@cFwhb;.A(8*D.QmLkK]z,md0'HiOE\pyeiv_PACR+P:Cm.
 wq_%l':E:q]g-UCc>r&s@BVo'kFN;(\9PF22Myg5w%nUBWQ6MJJ#qL#w>2oxckP'H:\$9F"mxsz]Dg
 k{1`fTcP'Y$CgGnc^paTV$dzhVX<SVN1RPb="gz3>+;(U$;Eb)P<>G)g)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 30 Jan 2001 09:39:56 -0800
Sender: ovidiu@cup.hp.com
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

On Tue, 30 Jan 2001 11:37:58 -0500, 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?

I posted a patch in October that implements the 'resource' URL handler. Take a
look at it at in the patch queue for Cocoon1.

Ovidiu