Description Jim des Rivieres 2001-10-10 21:34:51 EDT

IResource.setLocal has problems. This method (which replaces ensureLocal
and scrubLocal) requires some form of connection to the VCM provider,
since the VCM provider is the only thing that could make a resource local.

Indeed, the whole notion of "local" resources requires VCM support and needs
to be reviewed.

NOTES:

JM (12/11/2000 10:24:05 PM)
	The only scenario in which non-local resources makes sense is one 
involving a VCM.
	setLocal does not replace ensureLocal.  It is there to support the VCM 
fetching content 
	and then telling the workspace that it should expect to see the content 
in the file system.
	Similarly, with scrubLocal.  It is expected that the VCM itself is the 
one that does the 
	dirty work of adding/deleting the content in the file system.  

jeem (12/13/00 7:01:26 PM) - Where are ensureLocal and scrubLocal? They don't 
appear
in the API any more (they were there in tech preview).

JM (01/02/2001 11:32:24 AM)
	These notions should be related to the VCM.
	Moving to BB for consideration.

KM (4/6/01 3:49:13 PM)
	Only sender that calls it with 'false' is ScrubLocalAction, which looks 
like it can be deleted.
	We are not making use of this core feature since neither CVS nor CC 
benefits from it.
	I am concerned then it may not even work given there are no senders 
of 'false'.
	Nothing to be done about this right now, moving to future.

JM (06/04/2001 6:58:28 PM)
	There likely are test suites which test the (false) case.
	This is both legacy and future expansion.  The VCM model does not 
require one to 
	have all resources local.  CVS and CC appear to have a model where 
everything is local.  
	Things like VSS do not use this model.  I believe that PVCS and 
Perforce do not require you
	to have everything local but that is fuzzy for me.  DAV does not 
specify either way as
	it is a protocol.  It is easy to see both modes of operation (i.e., 
both "I GET the whole project" and 
	"I GET only what I need").  
	Regardless, the setLocal functionality relates to modeling resource 
existance 
	without actualy being forced to fetch the resource.

	So, this is core API which is related to part of the VCM model which is 
not yet fully implemented.
	If you have a particular concern about the API being there, we can 
remove the it until VCM 
	implementations for VSS, DAV, ... are being done and determine that 
they need the behaviour.