TL;DR: The whole point is the new API in ez-rpc.h, check it first, no need to review the rest if the API is bad
This is an exploration around the EzRpc API, to see if it can be extended to support arbitrary streams (enabling e.g. tls, gzip, websocket). It adds:
- An
EzRpcClient
constructor without a stream, which can be set later withEzRpcClient.setStream()
- A constructor to create an "empty"
EzRpcServer
(without a stream and without anacceptLoop
) - An
EzRpcServer.addStream()
function to add streams to the server object (those streams can come from an externalacceptLoop
).
@kentonv: I really don't want to lose your time with stupid propositions, so feel free to close if this seems useless/convoluted
Note: pretty sure I messed up with the PromiseAndFulfiller
, happy to get advice there