Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 25011 invoked by uid 500); 10 Jul 2003 10:39:56 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 24990 invoked from network); 10 Jul 2003 10:39:56 -0000 Received: from adsl203-150-253.mclink.it (HELO linux.local) (213.203.150.253) by daedalus.apache.org with SMTP; 10 Jul 2003 10:39:56 -0000 Received: from apache.org (localhost [127.0.0.1]) by linux.local (Postfix) with ESMTP id 73A6684D36 for ; Thu, 10 Jul 2003 12:39:55 +0200 (CEST) Message-ID: <3F0D427A.8030009@apache.org> Date: Thu, 10 Jul 2003 12:39:54 +0200 From: Gianugo Rabellino User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: DirectoryGenerator source-oriented refactoring References: <3F0D2CA9.2020005@apache.org> <3F0D391E.4070202@anyware-tech.com> <3F0D3DAE.9040205@apache.org> <3F0D40D7.8040407@anyware-tech.com> In-Reply-To: <3F0D40D7.8040407@anyware-tech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sylvain Wallez wrote: > > My cache implementation deals with SourceValidity instead of > lastModified(), which allows caching for sources where lastModified > isn't available (e.g. a CVS directory, or a tagged CVS source which can > go back in time if the tag is moved). Also, I added a "directories-only" > parameter which automatically filters regular files (it can be > needlessly expensive to get infos on them and later discard them in the > pipeline). > > But my implementation started from the 2.0 DirectoryGenerator which > hasn't all the fancy sort stuff. So I think a merge is actually what's > needed. Be my guest. ;-) If I can be of any help, just let me know. > And while we're at refactoring, what do you think of having separate > regexps for directories and files ? This would be really useful since > their respective naming rules are totally different. E.g. if I want only > .xml files, the regexp has to be "^[^.]*$|\.xml$", which looks quite > ugly when the file regexp would simply be "\.xml$". How do you plan to express that in the component configuration? I'm afraid it might start being overcomplicated... Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Now blogging at: http://blogs.cocoondev.org/gianugo/)