Post #2046411
2025-03-27 17:45 UTC
@atlauren That probably deserves another thread. The short version of that story is…
I was the engineer working on webdavfs from the end of Mac OS X 10.1 through the 10.4 updates. I left the Mac OS X file systems team right as 10.4 shipped because I was told that none of the things I wanted to improve in the code were going to be approved, and I’d be assigned to work on other things.
What made the Finder *seem* slow was a limitation of HTTP. Entire files that had been written to had to be pushed up to the server with a PUT request when the file was closed. That time of pushing an entire file up to the server when a file had been written to and closed is what made the Finder seem unresponsive.
1/2
Replies (1)
-
@jimluther@techhub.social 2025-03-27 17:49
@atlauren Anyway, after I quit working on webdavfs, it never really got any faster but we came up with a way for webdavfs to communicate with the Finder to show progress during close on the PUT request to the server. Bill Conway, who had taken over responsibility for webdavfs and implemented that change in webdavfs. The Finder team showed that progress during close to let the user know something was happening during file copies. Sometimes showing something is happening in UI makes users *think* things are faster 😀 2/2