Re: [platform-vcm-dev] ISynchronizer

[Matt_Conway@xxxxxx]

On 04/17/2002 01:41:38 PM platform-vcm-dev-admin wrote:
> 
> The core API doesn't support this yet. I think there may already be a PR 
opened 
> for this. I assume that you are asking this because you want to update 
your 
> plugin with state changes made to resource in the local file system? An 
> alternate approach to have provide state information refreshed is to 
have a 
> provider specific action which does the refresh then a state refresh. 

Basically what I want is as follows:
For each Resource R, I want to have a Object (or session property) S, 
which contains some cached state (basically isCheckedOut, isRemote, etc)
Now, because this state is cached, it could get stale (i.e. if someone 
uses a CLI tool to check in a file), so I want the user to be able to 
update the Ss.  Rather than having my own mechanism I thought I would just 
tie into the "Refresh" action because most people seem to expect that a 
resource refresh should work for the plugins too.  Having my own mechanism 
wouldn't be hard to do, but I 'd rather not confuse users by giving them 
too much choice =)

Now in order for me to listen our for a refresh, I need to setup a 
ResourceChangeListener, but at the same time I don't want to update my 
cached info for all resource change notifications, because that would then 
defeat the purpose of caching to improve performance in the first place. 
Being able to determine a refresh vs plain resource changed would solve 
this.

Also, this is less of a issue, but it is possible that  a timestamp may 
not change (or get older) even though the contents of the file _have_ 
changed, so if a user knows this and chooses to refresh, that should cause 
all resources to refresh regardless of timestamp.  This is probably enough 
of an edge case to not matter though.

Matt