[
https://issues.apache.org/jira/browse/OLINGO-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861371#comment-13861371
]
Jens Huesken commented on OLINGO-105:
-------------------------------------
Hi,
I would not recommend to cache the ODataResponse. In case a resource did not
change on the server - which can be determined by an application (also with
caching) by analyzing the data (not the serialized) result - one should work
with mechanisms defined in HTTP.
(e.g. HTTP headers like Last-Modified or eTag). If a resource did not change on
the server, your application should respond with HTTP Status Code 304 (Not
Modified) - see also http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html.
I must admit it doesn't seem there is any convenience in the OData Library to
achieve this behaviour via raising an Http Exception (Not Modified) within the
processor. So I'll keep that issue open for further discussion.
Maybe you can also provide additional information if such a mechanism would
help.
Regards,
Jens.
> Not able to cache the ODataResponse
> -----------------------------------
>
> Key: OLINGO-105
> URL: https://issues.apache.org/jira/browse/OLINGO-105
> Project: Olingo
> Issue Type: Improvement
> Reporter: dhaval gupta
> Assignee: Jens Huesken
>
> Hi,
> Sometimes there is application need to cache the response when there are
> large number of users requesting the same data again and again.
> Now I am using Oracle coherence cache and I cannot cache the
> ODataResponseImpl because it does not implements the Serializable java
> interface and there is no serialVersionUID. To cache the class it should be
> serializable.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
