If you use gun a bunch, you've probably noticed the messages like "Hello
wonderful person :)" and "WARNING: This file.js module...".
This PR allows you to silence them.
Use `Gun.log.off = true` to bring peace back to your workflow.
> **Note:** great when used with file watchers like nodemon."
If the most recent gun options disable the file module, then it
won't try to read/write from the json. Previously it would. Also, now
you can override the behavior by passing `{ file: false }` as the
options in `gun.put`.
Fixes issue #259, where edits made offline wouldn't be queued for when a
socket comes back online.
I didn't quite follow the logic of the previous queuing system, so I
refined it and the issue was fixed, so.... yay!
Servers will now try to initiate a connection using websockets if the
`peers` option is set. Currently, it'll either start throwing errors,
or generate a broadcasting storm. Still work to be done...
This marks a milestone of getting the servers to connect to each
other. Now to have those messages make sense. Committing so I
have an easy rollback point.
The `wsp.server` logic was never making it to the /gun.js route. If the
browser is just sending a GET request for a the js file, it won't set
the upgrade property, and the server logic wouldn't let the request pass
if it didn't have that header.
I've simply moved the check below the file serving logic.
Sometimes you just wanna send data to only one client, not the whole
bunch. Now, with new advances in gun technology, you can disable the
default broadcasting behavior.
Feature implemented under the direction and guidance of @amark.
Hi, the window.localStorage gives an exception when you use it in Edge on localHost or from a file based html.
I've added a check for the localStorage.
The code is a snipped from here: https://mathiasbynens.be/notes/localstorage-pattern
