You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working on a Ring websocket API that's currently in experimental alpha. Would you be interested in a PR to support this in http-kit, to be merged when the Ring websocket API is stable? It would obviously be supported in conjunction with http-kit's native implementation.
The reason I'm asking this while the Ring API is still experimental is that I'd like to try implementing the API for different third-party adapters, so I can get feedback and forewarning of any design issues. I've submitted a similar issue to the ring-jetty9-adapter project.
The text was updated successfully, but these errors were encountered:
No problem! My current plan is to add a pongHandler to AsyncChannel, and create a PingMessage and PongMessage class for use with AsyncChannel.send, in order to allow the ping/pong support that the Ring websocket spec requires. Does this seem a reasonable approach?
I've been working on a Ring websocket API that's currently in experimental alpha. Would you be interested in a PR to support this in http-kit, to be merged when the Ring websocket API is stable? It would obviously be supported in conjunction with http-kit's native implementation.
The reason I'm asking this while the Ring API is still experimental is that I'd like to try implementing the API for different third-party adapters, so I can get feedback and forewarning of any design issues. I've submitted a similar issue to the ring-jetty9-adapter project.
The text was updated successfully, but these errors were encountered: