cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Upayavira" ...@upaya.co.uk>
Subject Re: CLI ideas (long)
Date Tue, 01 Apr 2003 22:25:55 GMT
> > [Nicola Ken - I didn't understand this bit of your reply:]
> > 
> >>Actually even the former is managed by Cocoon, I don't remember
> >>where but IIRC the Environment has such an info, only that in the
> >>current implementation of the CLI environments it's unimplemented.
> 
> I mean that the hook are already there, you just have to fill in the
> implementation.
> 
> In the Environment there is
> 
>      boolean isResponseModified(long lastModified);
>      void setResponseIsNotModified();
> 
> But it's never implemented. In AbstractEnvironment:
> 
>      public boolean isResponseModified(long lastModified) {
>          return true; // always modified
>      }
> 
>      public void setResponseIsNotModified() {
>          // does nothing
>      }
> 
> So it means that the above has to be first implemented, then used when
> writing to disk.

Okay. So how easy is it to code this? Any caching gurus out there?
 
> > As Nicola Ken pointed out, links of every page would need to be
> > cached, because when a page will be found to be already on disk and
> > uptodate, you still need the links for crawling. Hmm. 

I'll have to think more about this one. Not straight-forward.

> >>As points that are important, I would say in order:
> >>
> >>  1) make Cocoon *not* output the pages that have an error
> >>  2) make cocoon output xxxpagename.error.txt with the errors
> >>     of the 'xxxpagename' page (configurable)
> >>  3) make the report on broken links in XML so that it can be
> >>     added to the site (where to put it configurable)
> >>  4) make the content not regenerated if uptodate (very important
> >>     from a user perspective POV)
> >>  5) use ModifyableSource instead of Destination
> >>  6) others
> >>
> 1 is about not making error pages be printed out... for one thing IIUC
> it needs resourceUnavailable() to be configurable (write out or not),
> but I don't know if maybe there are other errors that write directly.

Sounds easy enough.
 
> 4 is quite important from a user perspective, but maybe it takes some
> time to do.
> 
> Feel really free in doing what you need/prefer, especially if other
> things take you too much time.

Progress will be slow, but I'll keep you posted.

Upayavira


Mime
View raw message