|
|
|
[
Permlink
| « Hide
]
Lars Torunski - [17/Nov/06 12:56 AM ]
Fabrizio, can you give us more details about the spec, e.g. chapter?
Fabrizio, currently I want to close this issue as a Won't Fix. Because
1) it is a MUST and not a HAVE TO 2) a developer can cache a page based on PUT or POST with special ICacheKeyProvider implementation; therefore the CacheFilter::isCacheable method should be backward compatible 3) you can reimplement the isCacheable method with your improvement request I have already reimplemented the isCacheable method,in order to use the filter in my rest-style web services,but I think would be better to make this behavior configurable by a filter parameter that, if missing, leaves the behavior unaltered, to complain your 2) .
e.g. parameter name=disableCacheOnMethods , parameter value=list of comma separated method names e.g. "POST,PUT,DELETE" An improvement instead of a bug ? Regard | |||||||||||||||||||||||||||||||||||||||