Files

Andrey Goncharov 37498ad5a9 Refactor server implementation for WebSockets

Summary:
Standardize WS implementation for JS environments.

Why do we need a separate server implementation for browsers?
Browser targets cannot authenticate via the default certificate exchange flow. For browser targets we verify the origin instead.
Moreover, for already forgotten reasons the initial implementation of the WS server for browsers used a different kind of message structure and added extra `connect`/`disconnect` messages. After examination, it seems the `connect`/`disconnect` flow is redundant.

Major changes:
1. Updated class hierarchy for WS server implementations.
2. Updated browser WS server to support the modern and the legacy protocols.
3. Now a websocket connection with the device is closed on error. The idea is it is highly unlikely to handle any subsequent messages properly once we observe an error. It is better to bail and reconnect. What do you think?

Reviewed By: mweststrate

Differential Revision: D31532172

fbshipit-source-id: f86aa63a40efe4d5263353cc124fac8c63b80e45

2021-10-21 03:34:15 -07:00

src

Refactor server implementation for WebSockets

2021-10-21 03:34:15 -07:00

package.json

Cleanup logger

2021-10-12 16:00:52 -07:00

README.md

Set up Flipper decapitated packages

2021-10-08 01:33:03 -07:00

tsconfig.json

Move files to flipper-common

2021-10-12 16:00:52 -07:00

README.md

flipper-common

Utilities that are shared between flipper-ui, flipper-server and flipper-plugin.