[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Repository polling and svnrobots.txt

From: Markus Schaber <m.schaber_at_codesys.com>
Date: Tue, 27 Jan 2015 08:20:44 +0000


Some of our clients[2] users want an automatic polling for updates and locks by other users.

To prevent the clients from "hammering" the servers, I want to implement some rate limiting. Is the svnrobotx.txt[1] the recommended way to allow such rate limiting to be configured by the server admins? Or are there other, similar specifications my client should respect (maybe in addition)?

(Remark: Due to the nature and culture of the world of IEC-61131-3 programming, most (if not all) our users only connect to their own corporate servers, it is rather unlikely to see them using public servers like SourceForge.)

[1] Used by Stephan Küngs SVNCommitMontior, see http://stefanstools.sourceforge.net/svnrobots.html
[2] CODESYS SVN, based on SharpSVN, see http://store.codesys.com/codesys-svn.html

Best regards

Markus Schaber

CODESYS® a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Product Development Core Technology
Memminger Str. 151 | 87439 Kempten | Germany
Tel. +49-831-54031-979 | Fax +49-831-54031-50
E-Mail: m.schaber@codesys.com | Web: http://www.codesys.com | CODESYS store: http://store.codesys.com
CODESYS forum: http://forum.codesys.com
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received
this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure
or distribution of the material in this e-mail is strictly forbidden.
Received on 2015-01-27 09:21:28 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.