Commit 4dcd2044 authored by Kirill Smelkov's avatar Kirill Smelkov

.

parent a5758836
...@@ -45,8 +45,15 @@ ...@@ -45,8 +45,15 @@
// Wcfs client implements pins handling in so-called "pinner" thread(+). The // Wcfs client implements pins handling in so-called "pinner" thread(+). The
// pinner thread receives pin requests from wcfs server via watchlink handle // pinner thread receives pin requests from wcfs server via watchlink handle
// opened through wcfs/head/watch. For every pin request the pinner finds // opened through wcfs/head/watch. For every pin request the pinner finds
// corresponding mappings and injects wcfs/@revX/f parts appropriately. // corresponding mappings and injects wcfs/@revX/f parts into the mappings
// appropriately.
// //
// The same watchlink handle is used to send client-originated requests to wcfs
// server. The requests are sent to tell wcfs that client wants to observe a
// particular bigfile as of particular revision, or stop watching for it.
//
//
// Every FileH maintains
// //
// //
// //
...@@ -83,6 +90,7 @@ ...@@ -83,6 +90,7 @@
// (+) currently, for simplicity, there is one pinner for each connection. In // (+) currently, for simplicity, there is one pinner for each connection. In
// the future, for efficiency, it might be reworked to be one pinner thread // the future, for efficiency, it might be reworked to be one pinner thread
// that serves all connections simultaneously. // that serves all connections simultaneously.
// XXX (wcfs client-level file handle - see package overview) ?
// XXX locking -> explain atMu + slaves and refer to "Locking" in wcfs.go // XXX locking -> explain atMu + slaves and refer to "Locking" in wcfs.go
// //
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment