Login | Register
My pages Projects Community openCollabNet

Discussions > issues > [Issue 21] New - Patch for suspending status updates after startup or resume

svnnotifier
Discussion topic

Back to topic list

[Issue 21] New - Patch for suspending status updates after startup or resume

Reply

Author albinsunnanbo
Full name Albin Sunnanbo
Date 2011-01-16 12:57:21 PST
Message http://svnnotifier.t​igris.org/issues/sho​w_bug.cgi?id=21
                 Issue #|21
                 Summary|Patch for suspending status updates after startup or r
                        |esume
               Component|svnnotifier
                 Version|current
                Platform|All
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|PATCH
                Priority|P3
            Subcomponent|code
             Assigned to|vlar
             Reported by|albinsunnanbo






------- Additional comments from albinsunnanbo at tigris dot org Sun Jan 16 12:57:21 -0800 2011 -------
==========
Background
==========
Case 1:
When SVN Notifier starts up by Windows autostart the disk and network activity competes with other tasks
starting up at the same time. Together with other tasks starting up SVN Notifiers slows down the logon
process and delays the time until the user reaches a responding desktop.

Case 2:
When a computer resume from sleep or suspend SVN Notifier starts to check for updates (if the
statusUpdateTimer has expired during suspend) before the network is ready. SVN notifier detects this as
an error and quickly marks all projects with red errors until the next scheduled search is completed.

=============
Patch content
=============
The patch creates a pause-timer that pauses the regular statusUpdateTimer for a configurable time after
application startup and/or system resume.
It creates separate configurations for pause length and on/off for both application startup and system
resume in the Settings dialog.

================
Design decisions
================
The system resume functionality only listens to the PowerModeChanged event:
It would be possible to listen to System.Net.NetworkIn​formation.NetworkCha​nge.NetworkAddressCh​anged and
count interfaces with OperationalStatus.Up to find out when the network is actually available. That would
increase the complexity of the solution both when there are several different network interfaces (LAN +
WLAN) and with local repositories (both on local disk and on a network drive). It would also break the
existing functionality that the status goes read when the network connection is not available for a long
time. The decision was to not listen to NetworkAddressChanged.

============
Patch target
============
This patch should be applied to trunk revision 293.

« Previous message in topic | 1 of 3 | Next message in topic »

Messages

Show all messages in topic

[Issue 21] New - Patch for suspending status updates after startup or resume albinsunnanbo Albin Sunnanbo 2011-01-16 12:57:21 PST
     [Issue 21] Patch for suspending status updates after startup or resume albinsunnanbo Albin Sunnanbo 2011-01-16 12:58:24 PST
     [Issue 21] Patch for suspending status updates after startup or resume vlar Vlad Rudenko 2011-01-17 22:59:59 PST
Messages per page: