reiver
/
raft-format
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

initial commits

master
Charles Iliya Krempeaux 2024-01-20 08:54:15 -08:00
parent 46e141aca5
commit 33f47f74d1
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -31,6 +31,12 @@ Also none of these supports a ‘**view-source**’ learning style (as none of t
That is why the **zarf format** exists. That is why the **zarf format** exists.
The **zarf format** is a text-based format (in the same way HTTP/1.1 protocol is a text-based), so a programmer can look at **zarf** files (i.e., ‘**view-source**’) to understand it.
The **zarf format** is simple to create, thus making it easy to create an encoder.
The **zarf format** is simple to parse, thus making it easy to create a decoder.
## Extension ## Extension
Although **zarf** does _not_ require an extension (since it has magic-bytes), if a file-extension is used for a **zarf** file, it should use the `.zarf` extension (on systems where file-extensions are necessary). Although **zarf** does _not_ require an extension (since it has magic-bytes), if a file-extension is used for a **zarf** file, it should use the `.zarf` extension (on systems where file-extensions are necessary).