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

Polling revision numbers...

From: JGalarza <jgalarza_at_astromed.com>
Date: Tue, 24 May 2011 12:26:15 -0700 (PDT)

Ideally I want to create an internal web portal that displays certain files from a checked out directory. Mainly certain images/license that may or may not need updating by Product Managers and the like. The server in which this portal will live will have the directory but that dir needs to be updated, not constantly, before they commit a new image/license and I'd rather not this when the log in or right before they update because our commits can be rather large (speed and performance of portal are essential).

My first thought is that constantly sending the 'update' command may bog down the server, even intermittent calls during a session may prove to be too much. I'm worried about this because we have other living applications on the server (which may or may not include our SVN later).

My questions are:

A) Is there a process hit from the Update command and the number of times called? If no then is it bad form to call the update command almost constantly during a session?

B) Is there a way to ask for ONLY the revision number of my branch and the main tree? This is so I can manually decide if I should call the update during the session and I don't really have the resources to hash through the revision log to find out every time I send 'update'.

C) If the answer to B is "no there is not a way" and "A" is "there is a performance hit" or "sending 'update' constantly is a terrible thing to do" then can I request this as a feature or possibly there is some 3rd-party DLL/app/service/etc that can do this for me?

Thank you.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-05-24 21:27:28 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.