2014/1/8 kuseman <[email protected]>: > Hi, > > I built a small handy feature that allows to cache cxf requests. > > Please check it out at: > > https://github.com/Viskan/com.viskan.cxf.cache > > Please fork, fix and come with improvement suggestions.
Thanks. I guess that the most important think in this project is how the cache is implemented. One thing that I like is the default cache implementation uses headers to generate the cache's selector key I don't know much about other software caches ( web cache, proxy cache) but I think that they usually don't take in account the Accept header, so * I guess* these caches only can hold one representation from a resource . But I'm not sure I would like that client could force to retrieve a fresh copy, by using some HTTP header in its request , For example, Pragma: no-cache ( or another header ). I know this depends on each cache implementation I don't like to use body for generating cache's selector key . Are you made any performance test with big messages ? IMHO, I think that POST requests should be cached , but I think that @Cacheable annotation is for that Regards
