Roadmap v5

[darrachequesne]

Here is the list of changes for the next major version of Socket.IO. This list is obviously up for discussions, so please do not hesitate to comment here.

• remove the reference to the handshake request (socket.request)

Rationale: keeping a reference to the http.IncomingMessage increases the memory footprint. Note: we should provide an alternative to be used with express-session and such.

Related: #3792

• when calling io.close() do not close the HTTP server if it was not created by the library

Related: #4002 (reply in thread)

• use private properties ("#") in order to improve the minification of the client bundle

Note: we might need to drop support for some older versions of Node.js.

Update: using private class fields does not significantly reduce the bundle size after minification + gzip (and is a breaking change since it is only supported starting with Node.js 14.6.0) so this change makes little sense for now.

• remove the "error" event emitted by the socket object

Related: #2047

Update: fixed in 15af22f

• implement various quality of services: quality of service features #3649

Rationale: currently we have "at-most-once" semantics, possibly "at-least-once" with acknowledgements and manual retry, but we could provide additional guarantees. Might be linked to #4510

Update: implemented in socketio/socket.io-client@655dce9

• prevent users from shooting themselves in the foot with socket.leave(socket.id);

Related: #4524

[...]

[qiulang]

Hi what about [RFC] Lite javascript client #4393

[darrachequesne]

That's a great idea! It should be independent from v5 though.

[655452]

That's really greate functionality

[giovanni-bertoncelli]

May I suggest to improve the usability of the RemoteSocket interface?
I fell in a lot of issues by not knowing how to properly handle a remote fetched socket...
My proposal would be to:

• Add a documentation page for RemoteSocket explaining:
  • RemoteSocket cannot have listeners attached
  • RemoteSocket ACKs behave differently (timeout is required, see Add timeout method to remote socket #4558)
  • CheatSheet for RemoteSocket (?)
• Add quick ways to distinguish between Socket and RemoteSocket (some isRemote flag or similar)

I've opened also a discussion about this some time ago: #4807

[darrachequesne]

Thanks for the heads-up, I will add this to the documentation.

[giovanni-bertoncelli]

Thank you!