[
https://issues.apache.org/jira/browse/CMIS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049726#comment-14049726
]
Florian Müller commented on CMIS-818:
-------------------------------------
I think a LastModifiedObjectInFolderContainerList approach wouldn't help. The
server would still need to compile the complete result set because the check if
this result set should be send to the client or if the server should respond
with the status code 304 is done after getDescendants (for example) has been
called.
Checking and setting headers in a service wrapper is possible today. What's
missing is a way of setting a different status code (304). Maybe we can
introduce a marker interface, which tells the OpenCMIS framework to stop
processing the request and let the service wrapper handle the response. The
problem with this approach is that the service wrapper implementation then has
to deal with the different bindings.
> Navigation services should support Last-Modified/If-Modified-Since Headers
> --------------------------------------------------------------------------
>
> Key: CMIS-818
> URL: https://issues.apache.org/jira/browse/CMIS-818
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.11.0
> Reporter: Ron Gavlin
> Assignee: Florian Müller
>
> AtomPub and Browser navigation services including getChildren, getFolderTree,
> getDescendants, and potentially the others should support
> Last-Modified/If-Modified-Since Headers.
> Some repositories have built-in caching mechanisms to track whether a folder
> tree has been modified. Since many of the Navigation services often require
> significant server-side resources, repositories with these built-in caching
> mechanisms should be able to leverage them with OpenCMIS. Currently, the
> OpenCMIS NavigationService does not provide hooks to implement such
> optimizations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
