You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2016/05/06 15:24:13 UTC
[jira] [Updated] (FC-43) Caching entries we have already fetched
could save a lot of time
[ https://issues.apache.org/jira/browse/FC-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated FC-43:
--------------------------------
Fix Version/s: (was: 1.0.0)
1.0.1
> Caching entries we have already fetched could save a lot of time
> ----------------------------------------------------------------
>
> Key: FC-43
> URL: https://issues.apache.org/jira/browse/FC-43
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 1.0.0-RC39
> Reporter: Emmanuel Lecharny
> Fix For: 1.0.1
>
>
> It's not an urgent change, but we fetch entries from the server that we already have fetched while processing a Manager operation. It would be interesting to cache those entries. Not sure how that would fit if teh server is updated by another client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)