tailscale/drive
Percy Wegmann 7209c4f91e drive: parse depth 1 PROPFIND results to include children in cache
Clients often perform a PROPFIND for the parent directory before
performing PROPFIND for specific children within that directory.
The PROPFIND for the parent directory is usually done at depth 1,
meaning that we already have information for all of the children.
By immediately adding that to the cache, we save a roundtrip to
the remote peer on the PROPFIND for the specific child.

Updates tailscale/corp#19779

Signed-off-by: Percy Wegmann <percy@tailscale.com>
2024-05-10 15:19:44 -05:00
..
driveimpl drive: parse depth 1 PROPFIND results to include children in cache 2024-05-10 15:19:44 -05:00
drive_clone.go tailscale: update tailfs file and package names (#11590) 2024-04-02 13:32:30 -07:00
drive_view.go tailscale: update tailfs file and package names (#11590) 2024-04-02 13:32:30 -07:00
local.go tailscale: update tailfs functions and vars to use drive naming (#11597) 2024-04-03 10:09:58 -07:00
remote_nonunix.go tailscale: update tailfs file and package names (#11590) 2024-04-02 13:32:30 -07:00
remote_permissions_test.go tailscale: update tailfs file and package names (#11590) 2024-04-02 13:32:30 -07:00
remote_permissions.go ipn/ipnlocal: only show Taildrive peers to which ACLs grant us access 2024-04-24 17:49:04 -05:00
remote_test.go drive: move normalizeShareName into pkg drive and make func public (#11638) 2024-04-05 11:43:13 -07:00
remote_unix.go tailscale: update tailfs file and package names (#11590) 2024-04-02 13:32:30 -07:00
remote.go drive: use secret token to authenticate access to file server on localhost 2024-05-03 09:03:32 -05:00