Decompose Client and Transport

[tshemsedinov]

Decompose Client and Transport for browser and server-client implementations

[zpwebbear]

Hello @tshemsedinov ! I want to clarify scope of work and will try to rephrase your task with my own words. Please approve or deny mu suggestions.

About Transport. Currently it's bound to EventEmitter and definitely can be used only in the server environment.

class Transport extends EventEmitter {
  constructor(server, req) {
    super();
    this.server = server;
    this.req = req;
    this.ip = req.socket.remoteAddress;
  }
/*...*/
}

And then HttpTransport WsTransport both extends Transport. From this point of view it seems that we want to have BrowserHttpTransport, ServetHttpTransport, and so on, at the end of the refactoring. BrowserHttpTransport will be based on the browser fetch and ServerHttpTransport will be still based on the EventEmitter.

Is the vector of my thoughts correct?