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

RE: Re: Status information -- needs a better solution

From: Michael Bloomfield \(EDS\) <mbloomfield_at_solutionsiq.com>
Date: 2006-02-03 00:41:50 CET

Why do people use network shares for development?

Our company has a central share for hosting svn. Each of us works on a
laptop (we're consultants). When we're connected, we do SVN Update and
SVN Commit... My working copy is on my laptop.

Before we disconnect from the network, we do SVN Update, then
disconnect, travel, work at Starbucks, whatever. Next time we connect
to the network, we do SVN Commit...

It works very well.

Maybe you have reasons for using a network share. Yet, TortoiseSVN
works very well when you have a local working copy on the
laptop/desktop. I would avoid using network shares for working copies.

***** (5 stars) for TortoiseSVN.

For me, if the refresh for icon overlays seem a little slow, I hit F5
to force Explorer to refresh. Does the trick every time for me.

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Thursday, February 02, 2006 1:52 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Status information -- needs a better solution

Jared Armstrong wrote:
> What I was discussing is happening without the left tree view even
> being visible. I understand that EXPLR is rather un-intelligent with
> the left tree panel updates.
>
> I am using 1.3.1 Build 5521, with SVNServe 1.3.0 on a network drive
> mapping. I really do almost all of my development work on network
> shares.

Ok, now it's clear why you don't have always up-to-date status
overlays.
You see, on network shares, it's the server that does the monitoring.
And the server is responsible for sending notifications about changes
of
files to the clients. But those notifications have a very low priority

on the server - other serving tasks (sending files, websites, ...)
come
first. Sometimes a server even drops change notifications.
Also, those notifications are sent unacknowledged, so if a packet is
lost, neither server nor client will notice that - and that means the
cache simply doesn't know about a change and won't update the status.

There's nothing I can do about that, sorry.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Feb 3 00:41:58 2006

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

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