Web socket client used in browser frontend. Designed to talk with uci-websocket and use the UCI packet format

Go to file

David Kebler a21aa3bf88 0.1.8 refactored to match .3.9 uci-websocket supports promise connect and auto reconnect with authentification (default is token emits 'status' events so client can monitor socket status the example client now uses quasar 1+ and is designed to work with example server in the uci-websocket repo also uses npm-watch dev dependency for restarting example client with changes in the consumer socket emit consumer-connection events		2019-09-16 18:24:08 -07:00
example/client	0.1.8 refactored to match .3.9 uci-websocket	2019-09-16 18:24:08 -07:00
src	0.1.8 refactored to match .3.9 uci-websocket	2019-09-16 18:24:08 -07:00
.eslintrc.js	refactored from simple built in client to reconnecting client package so client will autoreconnect if sockect server goes down/up.	2019-02-26 12:07:16 -08:00
.gitignore	0.1.7 Update Deps - created example folder and put in server and client (v1+ quasar) matched examples. Change scripts in package.json to run examples add @uci/websocket as a dev dep.	2019-08-13 09:16:43 -07:00
.npmignore	0.1.7 Update Deps - created example folder and put in server and client (v1+ quasar) matched examples. Change scripts in package.json to run examples add @uci/websocket as a dev dep.	2019-08-13 09:16:43 -07:00
nodemon.json.off	0.1.8 refactored to match .3.9 uci-websocket	2019-09-16 18:24:08 -07:00
package.json	0.1.8 refactored to match .3.9 uci-websocket	2019-09-16 18:24:08 -07:00
readme.md	refactored from simple built in client to reconnecting client package so client will autoreconnect if sockect server goes down/up.	2019-02-26 12:07:16 -08:00

readme.md

UComandIt Websocket Class for Browsers sending and receiving JSON packets

What is it

TL/DR;

What's it good for

Why Bother

Getting Started