Map Server Session events to Client methods

My final goal is to be able to pipe a Session from a ssh2.Server Session to a ssh2.Client (once authenticated).
That way I can pipe to multiple Client for example.

For most of the Server Session events, it's easy to map them to a Client method.

However there are few requests that are sent internaly in during Client.shell() or Client.exec().
It's all the todo stack that can call reqAgentFwd, reqPty, reqX11 (same in the shell() method)

In the Server, these events (for example the ptyevent) are associated to a client Session and they can theoricaly be emitted multiple times I guess. But the Client cannot send them multiple time actualy.

Also does this mean that only one "real session start" requests should be received by Session ? But it seems the server can handle more than one per Session.

Thanks !

Start by comparing the Session events described in the v0.8.9 README with the request handling in lib/client.js, especially Client.shell(), Client.exec(), reqAgentFwd, reqPty, and reqX11. Then inspect the corresponding session handling near lib/server.js#L804. Done requires a clear, tested mapping of server Session events to Client methods and an answer for repeated session requests.