Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: [design] Cocoon Blocks 1.1
Date: Fri, 15 Nov 2002 08:04:03 +0100
Message-ID: <GMEBIBHGAOFGJCDPJANDKEFDFLAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
Importance: Normal
In-Reply-To: <3DD41939.20100@apache.org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"


Stephen McConnell wrote:
> >
> >Do you mean this (I guess not ;) )?
> >
> 
> I think we are saying the same thing.
> 
> :-)
> 
Great! ;)

> Assuming that we don't want to expose blocks in a classloader to the 
> client - instead what we want is a expose of the services that a block 
> provides to the client.  However, as pointed out in several of the 
> messages on this topic, there is a requirement for the overloading of 
> the result of URI based resource resolution.  Given the principal of 
> seperation of the block (in terms of client accessibility), then a 
> service is needed against which resources can be resolved based on 
> supplied URIs (as distinct from classloader based access to resources).
> 
Yes, that's right.

Now, as we all agree...we only have to get 2.1 out of the doors...

Carsten

 
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org