[
https://issues.apache.org/jira/browse/CMIS-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301377#comment-14301377
]
Florian Müller commented on CMIS-888:
-------------------------------------
It is actually possible today, but not straight forward. You would have to
configure a custom binding and provide your own RepositoryService
implementation, which returns a stored repository info instead of fetching it
from the server.
But keeping (or serializing) the session object is much better if you want to
keep the amount of calls small. The session object also holds the type cache.
If you can assume that the type definitions don't change, there is no need to
fetch the type definitions again and again for each session. If you would just
cache the repository info, OpenCMIS would still have to reach out to the server
for the type definitions and produces overhead that you don't want and need.
> Make RepositoryInfo Cacheable
> -----------------------------
>
> Key: CMIS-888
> URL: https://issues.apache.org/jira/browse/CMIS-888
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-client-bindings
> Affects Versions: OpenCMIS 0.12.0
> Reporter: Francesco Uliana
> Priority: Minor
>
> each time I create a new org.apache.chemistry.opencmis.client.api.Session
> with
> org.apache.chemistry.opencmis.client.runtime.SessionFactoryImpl#createSession(..)
> the cmis client perform an HTTP GET request to
> "/alfresco/api/-default-/public/cmis/versions/1.1/atom?repositoryId=-default".
> The response from alfresco is always the same, could you allow some kind of
> policy to cache globally RepositoryInfo?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
