[
https://issues.apache.org/jira/browse/SVN-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527380#comment-16527380
]
Julian Foad commented on SVN-4754:
----------------------------------
One of the main points brought up in discussion on the dev mailing list was a
warning about the general unreliability of filesystem watching services.
_Date: 2018/06/25, From: Julian Foad, Subject: "#4754: Status Cache", archived
[on
lists.apache.org|https://lists.apache.org/thread.html/2a09f117e651f7cf7d6a1f1278624ba448ea00c602ec7eebed33f4d7@%3Cdev.subversion.apache.org%3E]_
> Status Cache
> ------------
>
> Key: SVN-4754
> URL: https://issues.apache.org/jira/browse/SVN-4754
> Project: Subversion
> Issue Type: New Feature
> Reporter: Julian Foad
> Priority: Major
>
> Core svn should provide a way to cache WC status results, so clients can get
> a quick answer to questions like "is the WC modified?"
> Finding the WC status (local modifications) in core svn currently requires
> crawling the selected subtree in the filesystem to check the modification
> dates and sizes of all files, to see whether any files are modified. The API
> is svn_wc_walk_status().
> Subversion GUI clients like Cornerstone and TortoiseSVN want to know
> instantly whether a given directory contains any local modifications, in
> order to grey-out or hide buttons like "Shelve" and "Commit" and "Revert"
> and/or to show status icons. TortoiseSVN implements its own status cache for
> this reason. Cornerstone does not yet, and would like to offer an instant
> visual status indication.
> A status cache could be updated by integrating with a filesystem "watching"
> service where one is available (FSEvents API on Mac, inotify on Linux, etc.),
> or by (more or less continuous) background scanning.
> The command-line client should be able to benefit from such a cache as well,
> if built with an appropriate watching or scanning module.
> It's a really old problem. I was surprised I could not find an existing
> issue, except for SVN-3038 "caching out-of-date (remotely modified) status"
> which is a subset or extension of the basic issue (and was closed due to lack
> of understanding, from lack of appropriate discussion, in my opinion).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
