Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <001701c33bce$a580f6a0$d20f3551@yachting>
From: "yachting heritage" <contact@yachting-heritage.com>
To: <forrest-dev@xml.apache.org>, <nicolaken@apache.org>
References: <3EF940FB.5090208@c-s.fr> <3EFAB220.26207.22B1EAEA@localhost>
 <3EFAACD5.9020700@apache.org>
Subject: Re: residuals of MIME type bug ?
Date: Thu, 26 Jun 2003 11:35:21 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

how could we avoid to received your bloody mail ?
----- Original Message ----- 
From: "Nicola Ken Barozzi" <nicolaken@apache.org>
To: <forrest-dev@xml.apache.org>
Sent: Thursday, June 26, 2003 9:20 AM
Subject: Re: residuals of MIME type bug ?


>
> Upayavira wrote, On 26/06/2003 9.43:
>
> > There are quite a lot of new features in the Cocoon CLI that Forrest
isn't using, for
> > example the option to switch off mime-type checking, and to only scan
pages once
> > (i.e. not using the link-view) to follow links.
>
> We have to use them, I agree. In fact Forrest was the promary use case
> of having more speed with the new CLI and for not using the mimetype
thing.
>
> > I believe there are still some problems with these new features in the
CLI, but it
> > should be possible to fix these. [For example, links being gathered on
pipelines
> > referenced via cocoon: protocol - I've found why, but not yet fixed it].
> >
> > Is anyone interested in looking into how to upgrade Forrest to use these
new
> > features?
> >
> > I think that doing this would stand a chance of resolving all of Luc's
problems, and
> > give me some people to do some solid debugging of the CLI.
> >
> > Any takers?
>
> -- 
> Nicola Ken Barozzi                   nicolaken@apache.org
>              - verba volant, scripta manent -
>     (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>