> This sort of behaviour is apparently already available in
> some clients, but it is very unfriendly to servers, particularly
> for large projects with many users.
>
> "There are now commercial Subversion clients that insist on
> doing repository scans on a periodic basis just to let people
> know when there's something new - and people are setting that
> to once a minute.
Whoever is the svn repository administrator, they can ask their users to
keep scanning down to a reasonable level, and enforce it if they need
to. That's the job for the administrator.
Also, since svn is internally revisioned, and only the finished result
of a status query is communicated to the client, a status query for a
large directory has essentially the same cost as a status query for a
single file.
I will admit, that if you are running subversion repository on some
internet-facing server, and you are tunneling through either ssh or
https, and you have thousands of people out there "watching" the
repository, you will have high cost to support all the encryption
overhead.
But some administrators would find this useful for their users and
choose to support it anyway.
To completely eliminate a feature because of the cases in which that
feature would be inefficient is a nonproductive behavior. Perfection is
the enemy of progress. If there grows a significant demand to support
the inefficient situation, then more development can happen at that
time, to make it more efficient.
For a software development company, who internally runs a repository and
distributes it internally with svnserve, you can easily support hundreds
of clients performing a status query for thousands of files, every
minute.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Apr 24 23:01:19 2006