Create a persistent tree that uses the given qualified name
as the key in the org.eclipse.core.resources.ISynchronizer.
It must be unique and should use the plugin as the local name
and a unique id within the plugin as the qualifier name.
Return the bytes for the variant corresponding the given local resource.
A return value of null means that no bytes have been stored
for the resource variant. It is up to the client to determine whether
this means that the resource variant does not exist or that it has not been
fetched or otherwise determined yet.
Set the bytes for the variant corresponding the given local resource.
The bytes should never be null. If it is known that the remote
does not exist, deleteBytes(IResource) should be used instead.
If the sync bytes for the remote are stale and should be removed,
flushBytes(IResouce, int) should be called.
Remove the bytes from the tree for the resource variants corresponding to the
given local resource and its descendants to the given depth.
After the bytes are removed, getBytes(resource) will
return null for the affected resources.
Return whether the resource variant state for this resource is known.
This is used to differentiate the case where a resource variant has never been fetched
from the case where the resource variant is known to not exist. In the later
case, this method returns true while getBytes returns null
resource - the local resource
whether the resource variant state for this resource is known
This method should be invoked by a client to indicate that it is known that
there is no remote resource associated with the local resource. After this method
is invoked, isVariantKnown(resource) will return true and
getBytes(resource) will return null.
Run the given action which may contain multiple modifications
to the byte store. By default, the action is run. Subclasses
may override to obtain scheduling rules or batch deltas (if
the byte store modifies workspace resources).