Commit 8e8434f441e3e179672053fbde29570a4fcf6981
notes about what works in web
Dominic Tarr committed on 3/25/2019, 8:15:08 PMParent: d57abeb1a15613d75868a07880475ed1fad140eb
Files changed
| README.md | changed |
| README.md | |||
|---|---|---|---|
| @@ -6,8 +6,25 @@ | |||
| 6 | 6 … | ||
| 7 | 7 … | removes everything not strictly needed for ssb-db, the goal being enough features to support | |
| 8 | 8 … | replication, but compatibility with the current application stack is out of scope. | |
| 9 | 9 … | ||
| 10 … | +## compromises for the browser | ||
| 11 … | + | ||
| 12 … | +I took some shortcuts to get this working in the browser quickly. | ||
| 13 … | + | ||
| 14 … | +* uses flumelog-memory (this does have persistence, but keeps everything in working memory. This is okay for small scale) | ||
| 15 … | +* removed all level based indexes. Currently no way to request replies or messages by type. Only message by key and messages in receive order. | ||
| 16 … | +* all other indexes changed to use flumeview-reduce (because then there was only one thing to polyfil) | ||
| 17 … | + | ||
| 18 … | +This current version works, but isn't gonna scale well to lots of data. It would be good to use | ||
| 19 … | +it for a new network, but harder to make it compatible with the current ssb network. | ||
| 20 … | +(however, I believe we'll get there) | ||
| 21 … | + | ||
| 22 … | +Also, some problems I noticed: | ||
| 23 … | + | ||
| 24 … | +* the javascript is really big. It's mostly libsodium-wrappers though, which is 1.3 mb. I think | ||
| 25 … | + we get that down to 200k though. | ||
| 26 … | + | ||
| 10 | 27 … | ## Example | |
| 11 | 28 … | ||
| 12 | 29 … | In this example, we create a feed, post a signed message to it, then create a stream | |
| 13 | 30 … | that reads from the feed. | |
| @@ -375,5 +392,4 @@ | |||
| 375 | 392 … | ## License | |
| 376 | 393 … | ||
| 377 | 394 … | MIT | |
| 378 | 395 … | ||
| 379 | - | ||
Built with git-ssb-web