Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
neo
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Labels
Merge Requests
2
Merge Requests
2
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Jobs
Commits
Open sidebar
Kirill Smelkov
neo
Commits
8df8538e
Commit
8df8538e
authored
Jun 26, 2018
by
Kirill Smelkov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
.
parent
097387c1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
go/wcfs/wcfs.go
go/wcfs/wcfs.go
+3
-3
No files found.
go/wcfs/wcfs.go
View file @
8df8538e
...
...
@@ -131,7 +131,7 @@
// from ZODB server through regular ZODB invalidation channel (as it is ZODB
// client itself). Then, before actually updating bigfile/<bigfileX>/head/data
// content in changed part, it notifies through bigfile/<bigfileX>/head/invalidations
// to clients that had opened this file (separately to each client) about the changes
// to clients that had opened this file (separately to each client) about the changes
:
//
// S: have <Sat>, δR(Sat_prev, Sat)
//
...
...
@@ -150,8 +150,8 @@
//
// When clients are done with bigfile/<bigfileX>/@<Cat>/data (i.e. Cat
// transaction ends and array is unmapped), the server sees number of opened
// files to bigfile/<bigfileX>/@<Cat>/data
is zero, and automatically destroys
//
bigfile/<bigfileX>/@<Cat>/ directory
after reasonable timeout.
// files to bigfile/<bigfileX>/@<Cat>/data
drops to zero, and automatically
//
destroys bigfile/<bigfileX>/@<Cat>/ directory
after reasonable timeout.
//
//
// Protection against slow or faulty clients
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment