Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add functionality to handle frame with custom opcodes #27

Open
xanderdunn opened this issue Apr 30, 2021 · 0 comments
Open

Add functionality to handle frame with custom opcodes #27

xanderdunn opened this issue Apr 30, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@xanderdunn
Copy link

xanderdunn commented Apr 30, 2021

My WebSocket client is frequently receiving frames with unknown frame opcodes: [oatpp::web::protocol::websocket::AsyncWebSocket::handleFrameAsync(){HandleFrameCoroutine}]: Unknown frame. I would like to be able to inspect these frame opcodes to know what the opcodes are and potentially respond to them.

The suggested solution of creating a custom implementation of listenAsync is not currently possible because it accesses private members such as readFrameHeaderAsync.

@lganzzzo lganzzzo added the enhancement New feature or request label Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants