Distributed system information query tool.
Starbeamrainbowlabs
56939dcc24
By assigning a random connection ID during the initial hello that's both unique to every new connection regardless of target and consistent across both the connection initiator and acceptor, we can do string comparison to determine which string is greater than the other. In doing so, we can ensur the same connection is always terminated, thereby avoiding closing both connections by accident. |
||
|---|---|---|
| docs | ||
| lantern-build-engine@094e175740 | ||
| src | ||
| .gitignore | ||
| .gitmodules | ||
| build.sh | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
systemquery
Distributed system information query tool.
FAQ
Q: I see a scary native binary build system in the development dependencies!
A: You're probably referring to esbuild. If you install systemquery from npm, the build steps for the client-side javascript will already have been completed, thereby negating the need to install a native binary.
The advantage of using a build system for the client-side browser resources is significantly improved performance. With this approach, we get the benefit of a build system without needing to install a native binary on target machines which might be incompatible with the host machine's CPU architecture.