Fossil SCM

Updated an outdated reference to "SHA1" hashes in the unversioned content doc.

wyoung 2023-12-12 21:44 trunk
Commit 4d43560f668eaac4b2963c05198a86df89c1a31df0b0878212ab4c413cd91fe4
1 file changed +2 -2
+2 -2
--- www/unvers.wiki
+++ www/unvers.wiki
@@ -78,11 +78,11 @@
7878
CREATE TABLE unversioned(
7979
uvid INTEGER PRIMARY KEY AUTOINCREMENT, -- unique ID for this file
8080
name TEXT UNIQUE, -- Name of the file
8181
rcvid INTEGER, -- From whence this file was received
8282
mtime DATETIME, -- Last change (seconds since 1970)
83
- hash TEXT, -- SHA1 hash of uncompressed content
83
+ hash TEXT, -- SHA1 or SHA3-256 hash of uncompressed content
8484
sz INTEGER, -- Size of uncompressed content
8585
encoding INT, -- 0: plaintext 1: zlib compressed
8686
content BLOB -- File content
8787
);
8888
</pre></blockquote>
@@ -106,9 +106,9 @@
106106
is to send large, frequently-changing files. Appreciate the consequences
107107
before making each change.
108108
109109
There are two bandwidth-saving measures in "<tt>fossil uv sync</tt>".
110110
The first is the regular HTTP payload compression step, done on all
111
-syncs. The second is that Fossil sends SHA1 hash exchanges to determine
111
+syncs. The second is that Fossil sends hash exchanges to determine
112112
when it can avoid sending duplicate content over the wire unnecessarily.
113113
See the [./sync.wiki|synchronization protocol documentation] for further
114114
information.
115115
--- www/unvers.wiki
+++ www/unvers.wiki
@@ -78,11 +78,11 @@
78 CREATE TABLE unversioned(
79 uvid INTEGER PRIMARY KEY AUTOINCREMENT, -- unique ID for this file
80 name TEXT UNIQUE, -- Name of the file
81 rcvid INTEGER, -- From whence this file was received
82 mtime DATETIME, -- Last change (seconds since 1970)
83 hash TEXT, -- SHA1 hash of uncompressed content
84 sz INTEGER, -- Size of uncompressed content
85 encoding INT, -- 0: plaintext 1: zlib compressed
86 content BLOB -- File content
87 );
88 </pre></blockquote>
@@ -106,9 +106,9 @@
106 is to send large, frequently-changing files. Appreciate the consequences
107 before making each change.
108
109 There are two bandwidth-saving measures in "<tt>fossil uv sync</tt>".
110 The first is the regular HTTP payload compression step, done on all
111 syncs. The second is that Fossil sends SHA1 hash exchanges to determine
112 when it can avoid sending duplicate content over the wire unnecessarily.
113 See the [./sync.wiki|synchronization protocol documentation] for further
114 information.
115
--- www/unvers.wiki
+++ www/unvers.wiki
@@ -78,11 +78,11 @@
78 CREATE TABLE unversioned(
79 uvid INTEGER PRIMARY KEY AUTOINCREMENT, -- unique ID for this file
80 name TEXT UNIQUE, -- Name of the file
81 rcvid INTEGER, -- From whence this file was received
82 mtime DATETIME, -- Last change (seconds since 1970)
83 hash TEXT, -- SHA1 or SHA3-256 hash of uncompressed content
84 sz INTEGER, -- Size of uncompressed content
85 encoding INT, -- 0: plaintext 1: zlib compressed
86 content BLOB -- File content
87 );
88 </pre></blockquote>
@@ -106,9 +106,9 @@
106 is to send large, frequently-changing files. Appreciate the consequences
107 before making each change.
108
109 There are two bandwidth-saving measures in "<tt>fossil uv sync</tt>".
110 The first is the regular HTTP payload compression step, done on all
111 syncs. The second is that Fossil sends hash exchanges to determine
112 when it can avoid sending duplicate content over the wire unnecessarily.
113 See the [./sync.wiki|synchronization protocol documentation] for further
114 information.
115

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button