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
..
compositedav	drive: parse depth 1 PROPFIND results to include children in cache	2024-05-10 15:19:44 -05:00
dirfs	tailscale: update tailfs file and package names (#11590)	2024-04-02 13:32:30 -07:00
shared	drive: parse depth 1 PROPFIND results to include children in cache	2024-05-10 15:19:44 -05:00
birthtiming_test.go	tailscale: update tailfs file and package names (#11590)	2024-04-02 13:32:30 -07:00
birthtiming.go	tailscale: update tailfs file and package names (#11590)	2024-04-02 13:32:30 -07:00
connlistener_test.go	tailscale: update tailfs file and package names (#11590)	2024-04-02 13:32:30 -07:00
connlistener.go	tailscale: update tailfs file and package names (#11590)	2024-04-02 13:32:30 -07:00
drive_test.go	drive: actually cache results on statcache	2024-05-03 16:07:52 -05:00
fileserver.go	drive: use secret token to authenticate access to file server on localhost	2024-05-03 09:03:32 -05:00
local_impl.go	drive: actually cache results on statcache	2024-05-03 16:07:52 -05:00
remote_impl.go	drive: use secret token to authenticate access to file server on localhost	2024-05-03 09:03:32 -05:00