You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Johan Compagner (JIRA)" <ji...@apache.org> on 2007/03/14 17:07:09 UTC

[jira] Commented: (WICKET-385) Move HTTP caching features out of wicket.Resource

    [ https://issues.apache.org/jira/browse/WICKET-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480815 ] 

Johan Compagner commented on WICKET-385:
----------------------------------------

where is isCacheable everywhere used?
How does it go with sharedresources?
Because is isCacheable used without really getting the resource stream?



> Move HTTP caching features out of wicket.Resource
> -------------------------------------------------
>
>                 Key: WICKET-385
>                 URL: https://issues.apache.org/jira/browse/WICKET-385
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Jean-Baptiste Quenot
>         Assigned To: Jean-Baptiste Quenot
>             Fix For: 1.3
>
>
> * Add IResourceStream.isCacheable() (default to false in AbstractResourceStream)
> * Add lastModifiedTime handling in ResourceStreamRequestTarget

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.