[ 
https://issues.apache.org/jira/browse/CMIS-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dieter Guendisch updated CMIS-966:
----------------------------------
    Description: 
There are use cases where applications often request a bunch of small files 
from a CMIS repository (like e.g. icons for their webapp).
It would be helpful if OpenCMIS would a provide a cache for the content of 
files in a similar way it already provides a cache for the metadata of files.
Ideally this cache would:
- be bound to the current cmis session so that it goes along with the metadata 
cache
- be configurable in terms of size (e.g. I want to cache no more than 500MB)
- result in no http remote calls at all for cached objects (if metadata & 
content was cached for one particular object)

  was:
Configurable rate limiting of remote requests for use with TCK.

The TCK does a lot of requests (there is even a warning about that in the 
workbench). It would be nice to be able to run all tests, but at a slower speed.
This could be achieved with rate limiting client requests.
This might be useful outside of the TCK as well. For example a generic rate 
limiting client wrapper.


> Add content cache to OpenCMIS
> -----------------------------
>
>                 Key: CMIS-966
>                 URL: https://issues.apache.org/jira/browse/CMIS-966
>             Project: Chemistry
>          Issue Type: New Feature
>            Reporter: Dieter Guendisch
>            Assignee: Florian Müller
>
> There are use cases where applications often request a bunch of small files 
> from a CMIS repository (like e.g. icons for their webapp).
> It would be helpful if OpenCMIS would a provide a cache for the content of 
> files in a similar way it already provides a cache for the metadata of files.
> Ideally this cache would:
> - be bound to the current cmis session so that it goes along with the 
> metadata cache
> - be configurable in terms of size (e.g. I want to cache no more than 500MB)
> - result in no http remote calls at all for cached objects (if metadata & 
> content was cached for one particular object)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to