[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] ISynchronizer
|
On 04/16/2002 10:40:17 PM platform-vcm-dev-admin wrote:
>
> Another lighter weight mechanism for associating data with resources is
by
> using IResource session properties. We make use of session properties in
the
> CVS plugin as a cache for local resource state information, see the
> EclipseSynchronizer class in the CVS plugin for an example.
I think this is more what I was looking for - I just wanted an easy way to
cache for each resource some state that is expensive to generate, and have
the ability to trigger a recalculation if the user does a local refresh.
Which leads to my next question. I assume that a local refresh does
something like calling resource.refresh() on each resource in the project?
If this is the case, is it only resources that have changed that actually
cause some action to be taken via the ResourceChangeListener? And if so,
how do I distinguish betweeen a refesh and a change not associated with
refreshing? Thanks,
Matt
