I wish there was a per page cache time property.  That way dynamic
pages had shorter cache times.  Perhaps tags on page would adjust the
cache time setting for the page.

That way proper cache expiration times could be reported back to the
browser and components like yours could get an idea of how dynamic the
page content is.

On 10/14/07, Chris Parrish <[EMAIL PROTECTED]> wrote:
> Aitor Garay-Romero wrote:
> >   > I'm trying to figure out a way to track whenever a given page's
> >   > rendered  output may have changed.
> >
> >   Just curious, what functionality do you want to achieve with this?
> I am building a validator extension - I'll announce v0.1 here shortly.
> Initially, it will retain no memory of the tests - you just run it on a
> page to validate the markup and get handed the result.
>
> In future versions, however, I'd like to store the results of the
> validation (passed, failed, unknown, etc).  That way I could present a
> report/view to the users showing which pages been validated (and their
> results) and which haven't.
>
> As you've probably guessed, if I want to store whether the page is
> valid, I need to know if a page has changed so that I can change its
> status as 'unknown'.
>
> -Chris
>
> _______________________________________________
> Radiant mailing list
> Post:   [email protected]
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com
_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to