Loading Profile...
Caching together with remote updating/editing files
I'm using ExpanDrive together with TextMate. I'm editing the file environment.rb (yes, rails). Besides ExpanDrive and TextMate, I'm using an ssh Terminal.app connection to the folder of the rails application. If I there type svn update and somebody updated environment.rb, ExpanDrive & TextMate won't pick up these changes.
I'm using ExpanDrive 1.2.2.
I'm using ExpanDrive 1.2.2.
I’m using Vim to get around it
4
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Reposted from http://getsatisfaction.com/expandrive/topics/it_caches#reply_704833.
This behavior will be greatly improved very soon.
ExpanDrive uses the MacFUSE to create a file system on OS X. OS X itself automatically caches a lot of file data in the kernel, and in the past it was impossible to tell OS X to update its cache through MacFUSE. As a result, when a file or directory was modified “remotely” (ie, not through ExpanDrive), we couldn’t tell OS X to update its cache. Sometimes it would take up to 5 minutes for OS X to decide to refresh its data on its own. Not good, I know.
This past Monday (12/8/2008), MacFUSE 2.0 was released with dramatically improved kernel caching. We’ve been testing against the developer’s release of MacFUSE for some time now, and it looks awesome. We’re doing a thorough audit of our MacFUSE install / update system, and we’re going to push an update with the newest version of MacFUSE. Probably early next week.
If you don’t want to wait for our release, then you can upgrade MacFUSE on your own by downloading it directly from Google. It’s completely painless, and you’ll see the caching improvements as soon as it’s installed.
I’m excited
The company says
this answers the question
-
Inappropriate?Hi Tom,
You're in luck. This is a known bug with MacFuse, and we're in the process of fixing it right now. This fix is tied to MacFuse 1.6, so we can't really release it until then, but I hear from the Developers of MacFuse that it should be along soon. -
Inappropriate?Any progress on this? I'm having the same issue. Not feeling very lucky. -
Inappropriate?i'm desperately waiting on this as well. huge problem. -
Inappropriate?This bug is KILLING me at work. I've over-written other people's changes several times because I thought it had been fixed -- but it's not.
Is there an ETA at least? This is a huge killer flaw that makes Expandrive _almost_ unusable. -
Inappropriate?MacFUSE 1.9, in experimental developer release, now supports the feature we needed. ExpanDrive 1.2.11 [just release] adds experimental support to let us detect and update our cache if the file has been changed on the server.
-
Inappropriate?Reposted from http://getsatisfaction.com/expandrive/topics/it_caches#reply_704833.
This behavior will be greatly improved very soon.
ExpanDrive uses the MacFUSE to create a file system on OS X. OS X itself automatically caches a lot of file data in the kernel, and in the past it was impossible to tell OS X to update its cache through MacFUSE. As a result, when a file or directory was modified “remotely” (ie, not through ExpanDrive), we couldn’t tell OS X to update its cache. Sometimes it would take up to 5 minutes for OS X to decide to refresh its data on its own. Not good, I know.
This past Monday (12/8/2008), MacFUSE 2.0 was released with dramatically improved kernel caching. We’ve been testing against the developer’s release of MacFUSE for some time now, and it looks awesome. We’re doing a thorough audit of our MacFUSE install / update system, and we’re going to push an update with the newest version of MacFUSE. Probably early next week.
If you don’t want to wait for our release, then you can upgrade MacFUSE on your own by downloading it directly from Google. It’s completely painless, and you’ll see the caching improvements as soon as it’s installed.
I’m excited
The company says
this answers the question
EMPLOYEE
EMPLOYEE
