socketless
socketless copied to clipboard
Pomax
A framework and methodology for writing web socket RPC programs, without writing a single line of web socket or RPC code.
Switch https://github.com/Pomax/are-we-flying over to this, to find actual problems that need both bug fixes and additional test cases.
we're not switching to typescript, because we're not adding a build process. jsDoc works fine in all tools that support type analysis.
README.md are fine, but a web page is how you get eyeballs on something, which gets you users, which gets you feedback, which leads to improvements.
Now that Node.js natively supports standard websockets, we should be able to remove the `ws` dependency. Sure, it's only 150kb, but that's still 150kb we no longer need.
Because if we don't, _everything_ gets passed through, include data syncs, full object sets, etc. etc. which we really don't want.
While all the code needs to live in the one file in order for `generate-socketless` to work, we should still refactor the `router` and `__send` functions so that they do...
If a server → client sync fails, we need to fall back to a full data object transmission, with an appropriate test that covers that situation.
In order to offer users an additional mechanism to prevent remote calls to local functions that should stay inaccessible, it would be useful to add an optional `disallow accessing anything...
There is a bit of failure indirection going on due to the `getPage` error handler and then also the `getClasses` error handler, where both need to work with the test-level...