Version 3.2 (Upcoming)

[sirn-se]

Version 3.2

Status: Future

Confirmed

Server context

Server should have method to set context options, just as Client does.

Considered

Fibres

Server use of Fibres for coroutine handler

Configurable HTTP factory

Currently the internal, lightweight HTTP classes are used. Allow user to set any psr/http-message compatible factory to be used instead (internal will remain default).

HTTP/2 support

The WebSocket upgrade handshake rely on HTTP/1.1, unsupported in HTTP/2.
Introduce support for HTTP/2 handshake model.
https://datatracker.ietf.org/doc/html/rfc8441

Handshake error messages

Error message in response body on handshake failure

Subprotocol support

Library already support adding subprotocol in headers, and middlewares can be used to handle messages. But we also need to support custom opcode messages. See #8 for example.

Additional middlewares

• Deflate - Deflate compression of messages
• RateLimiter - Limit connections/ operation per connection
• PSR-15 Server Request wrapper middleware

Configuration

• Connection retry strategy