Which repository access method is used to create a new “working copy”, file:/// or svn:// in same machine?

The svn:// scheme goes to a socket. If you want to checkout directly from the filesystem, use the file:// scheme (you don't use the server in that case).

The svn:// scheme goes to a socket. If you want to checkout directly from the filesystem, use the file:// scheme (you don't use the server in that case). (You could use file://, svn://, svn+ssh://, or https:// to check out a working dir on the same machine, but except for file:// those all require running some kind of server.).

Djc,thankyou very much. – Banani Apr 8 '10 at 18:28.

If the users have file system access to the repository, they can use file://. However, this is probably a bad idea. The recommended practice for a multi-user environment is to set up svnserve and access the repository via the svn:// protocol (or or https:// as the case may be).

From the Choosing a Server Configuration section of the svnbook Do not be seduced by the simple idea of having all of your users access a repository directly via file:// URLs. Even if the repository is readily available to everyone via a network share, this is a bad idea. It removes any layers of protection between the users and the repository: users can accidentally (or intentionally) corrupt the repository database, it becomes hard to take the repository offline for inspection or upgrade, and it can lead to a mess of file permission problems (see the section called “Supporting Multiple Repository Access Methods�).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.