Bug 309967

Description Martin Oberhuber 2010-04-21 10:11:23 EDT

User Story:
As a user of an Eclipse based IDE who's working on very large projects, I want to apply a viewer filter that quickly shows only writable files, such that I can concentrate on the files I have modified.

We've had this feature in previous (non Eclipse based) tools using a file system cache, and it was widely used. In Eclipse though, the current Resources implementation requires such a "read-only filter" to call getResourceAttributes() for every element. On a project with 60000 files in total, of which only 10 are writable, this does not scale. Especially on a slow file system like a Clearcase dynamic view, a network share or an EFS shared web folder, just getting the fstat() of 60000 files can take minutes, which is not acceptable.

It would seem straightforward to have the refreshLocal() operation, which reads file state anyways, cache that information in the ResourceInfo object along with the modification timestamp. Optionally, this would also enable resource change events when read-only state changes on a refresh, such that viewers/filters can listen to such changes.

If adding read-only state to the ResourceInfo is being considered, adding the "is symbolic link" information to the ResourceInfo should be considered as well. Knowing what elements are actually symbolic links is critical for tracking aliasing through symbolic links as per bug 198291.