I have a question about Client Browser Cache. The cached response in
LightWeightBrowser is the marshalled response - which makes sense
because that is in keeping with the HTTP specification. This means that
even when there is a cache hit there is the overhead of unmarshalling
the response into the JAXB Entity. In our case this is typically 2-3 ms
in production environment, this is not big in itself except we can
potentially have 30-40 cache hits corresponding to a single end user
page request adding an overhead of up to 100ms. My question is:


*         Is it feasible to have a Client Cache implementation that
stores the marshalled entity instead? I am sure it is possible but do we
see any issues to having such a cache?

*         Does any such implementation already exist (and I wasn't able
to find it in the documentation)?





This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
Resteasy-users mailing list

Reply via email to