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

Go to file

David Kebler 7b7872cb64 add processing of pushed packets. The _header.id prop but be set to 'pushed' instead of id of the packet generated by send		2018-05-24 12:24:43 -07:00
.eslintrc.js	working web browser client (with quasar) uses json packets and specifically works with uci-websocket	2018-04-05 15:11:59 -07:00
.eslintrc.js.off2	working web browser client (with quasar) uses json packets and specifically works with uci-websocket	2018-04-05 15:11:59 -07:00
.gitignore	working web browser client (with quasar) uses json packets and specifically works with uci-websocket	2018-04-05 15:11:59 -07:00
.npmignore	working web browser client (with quasar) uses json packets and specifically works with uci-websocket	2018-04-05 15:11:59 -07:00
browser-client.js	add processing of pushed packets. The _header.id prop but be set to 'pushed' instead of id of the packet generated by send	2018-05-24 12:24:43 -07:00
package.json	add processing of pushed packets. The _header.id prop but be set to 'pushed' instead of id of the packet generated by send	2018-05-24 12:24:43 -07:00
readme.md	working web browser client (with quasar) uses json packets and specifically works with uci-websocket	2018-04-05 15:11:59 -07: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

"babel-eslint": "^8.2.1", "eslint": "^4.18.2", "eslint-config-standard": "^11.0.0", "eslint-friendly-formatter": "^3.0.0", "eslint-loader": "^2.0.0", "eslint-plugin-import": "^2.9.0", "eslint-plugin-node": "^6.0.1", "eslint-plugin-promise": "^3.7.0", "eslint-plugin-standard": "^3.0.1"