> I am not sure it is a good point, but in case it is useful: in linux
> console (command prompt) I to execute two commands in order to get all
> property values:
> 'svn list': it return all files and directories in a folder, each one
> on a separate line. Example: 'fileA fileB dirC fileD'
> Then I execute second command:
> 'svn proplist -v fileA fileB dirC fileD': all files provided as
> command line arguments.
> How much time it would take...
> Are these only two request to svn server or it is separate request for
> each file/directory...
That's one request for each listed file. Well, at least one request.
The svn proplist command only returns the name of the property.
Only if '-v' is specified, it will read the value of each property. And
that will take another round-trip to the server for every property.
> How much time svn server will take for 'proplist' command...
> Is there limitations about 'max length of command' or 'max number of
> command line arguments'...
There are limits for command line parameters. But that's not the issue
here (you can write the params to a temp file and just pass the path to
that tempfile instead).
The problem are the many round-trips to the repository which are
required to get (and show) the properties.
It won't be a big problem for repositories on the same LAN, but for
repos hosted somewhere else, this would render the repobrowser useless.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-09-08 16:49:16 CEST