Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3CF0C89D.1060604@anyware-tech.com>
Date: Sun, 26 May 2002 13:35:57 +0200
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9) Gecko/20020311
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [RT] InputModules for sitemap variables
References: <3CEE4787.90303@anyware-tech.com>
 <20020524161912.H31670@bremen.dvs1.informatik.tu-darmstadt.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Christian Haul wrote:

>On 24.May.2002 -- 04:00 PM, Sylvain Wallez wrote:
>
>>Now what about allowing the use of InputModules in sitemap variable 
>>substitution ? For this, we need to extend the variable naming scheme : 
>>if a variable name contains a colon (':'), the string before the colon 
>>identifies an InputModule, and the string after the colon identifies an 
>>attribute name for the InputModule (see InputModule.getAttribute())
>>
>
>It sounds like a cool idea, but the syntax would suggest that any
>source could be used. Indeed, modules are related to sources but offer
>a very different API and I like to think of them being "lightweight"
>sources. I don't think it would make sense to merge them for example.
>

I proposed the colon separator as it is what we are used to for 
namespaces prefixes and protocols (URL and sources). But this has 
nothing to do with sources protocols as it is used for substituing 
simple values and not large data streams provided by sources.

>Apart from that, yes, I think it would be cool.
>

:)

>>Chris, what about passing the full object model instead of just the 
>>Request to {Input, Output}Modules ? This would allow a wider range of 
>>implementations.
>>
>
>Possible. One could even create a (meta) module that accesses a
>source, then :-) Whoa, that would be a mind-boggling complicated data
>flow %-]
>

Correct me if I'm wrong, but my opinion is that modules have nothing to 
do with sources. Sources give access to a data stream (be it binary or 
SAX events) while modules give access to some simple values. The 
meta-module you're talking about would be very confusing.

>It does work to get more attention to your stuff moving it to
>trunk. Cool. :-)
>

Well, I actually had this idea before the move in the main trunk. But 
the move facilitates cross-component pollination !

Sylvain

-- 
Sylvain Wallez
 Anyware Technologies                  Apache Cocoon
 http://www.anyware-tech.com           mailto:sylvain@apache.org


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