aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/docs/love.txt
diff options
context:
space:
mode:
authorDavid Walter Seikel2014-05-28 16:15:21 +1000
committerDavid Walter Seikel2014-05-28 16:15:21 +1000
commit7666177682592afe8bbccc722e803aec69dd152b (patch)
tree10f31a0491fb345841a5cffb65f9550dd7df6afe /docs/love.txt
parentNo, this is not the portal The Naminator came through, this is much worse. B-) (diff)
downloadSledjHamr-7666177682592afe8bbccc722e803aec69dd152b.zip
SledjHamr-7666177682592afe8bbccc722e803aec69dd152b.tar.gz
SledjHamr-7666177682592afe8bbccc722e803aec69dd152b.tar.bz2
SledjHamr-7666177682592afe8bbccc722e803aec69dd152b.tar.xz
Run the docs through a spell checker. I usually use an editor that doesn't have one.
Diffstat (limited to 'docs/love.txt')
-rw-r--r--docs/love.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/love.txt b/docs/love.txt
index e21b18b..d95dc30 100644
--- a/docs/love.txt
+++ b/docs/love.txt
@@ -57,7 +57,7 @@ the major amounts of web infrastructure that already exists and already
57solves most of the problems that currently plague virtual worlds based 57solves most of the problems that currently plague virtual worlds based
58on SL tech. 58on SL tech.
59 59
60The down side of separated is that changes might be slower propogating 60The down side of separated is that changes might be slower propagating
61to the web server, and there might be two copies of any given set of 61to the web server, and there might be two copies of any given set of
62assets in memory at once. 62assets in memory at once.
63 63
@@ -127,7 +127,7 @@ inspired by git using SHA-1 hashes for content addressable assets.
127SHA-1 hashes are 40 character hex codes representing 160 bit numbers 127SHA-1 hashes are 40 character hex codes representing 160 bit numbers
128that are calculated based on the content. So the same content will give 128that are calculated based on the content. So the same content will give
129the same SHA-1 hash. Git has proved that you only need the first digits 129the same SHA-1 hash. Git has proved that you only need the first digits
130of the SHA-1 hash to ensure uniqueness, so it's feasable to use only the 130of the SHA-1 hash to ensure uniqueness, so it's feasible to use only the
131first 128 bits of SHA-1 hashes to squeeze it into a UUID for the 131first 128 bits of SHA-1 hashes to squeeze it into a UUID for the
132purposes of uniquely identifying assets. Precisely what git does. This 132purposes of uniquely identifying assets. Precisely what git does. This
133means it could be backwards compatible with LL's use of UUIDs. 133means it could be backwards compatible with LL's use of UUIDs.