Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3C12B278.4030100@hartle-klug.com>
Date: Sun, 09 Dec 2001 01:38:16 +0100
From: Michael Hartle <mhartle@hartle-klug.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:0.9.6) Gecko/20011120
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
CC: Ovidiu Predescu <ovidiu@cup.hp.com>
Subject: Re: [RT] Managing Flow and Resources
References: <200112090006.fB906Zk29262@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Ovidiu Predescu wrote:

>I'll let you know what's the progress on my work. If anyone is
>interested in seeing intermediate results, I can check the code in the
>scratch-pad CVS area.
>
I am definitely interested in seeing your results. I still have problems 
thinking the right way for Prolog or Scheme, but this implicit (right ?) 
approach might well be a breakthrough that we are all waiting for 
regarding this topic. I am only hoping that the approach itself won't be 
a bottleneck when it comes to serving content in a production 
environment - what do you think ?

Another question, is the current abstraction of a sitemap able to allow 
different principles of sitemaps (current one, scheme-based one, etc.) 
the admin/developer can choose from depending on his needs ? E.g., I'd 
use the current sitemap type at the root, mounting a scheme-based 
sitemap under /scheme, then in the scheme-based sitemap I'd mount some 
other sitemap type under /scheme/other and so on.

Best regards,

Michael Hartle


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