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

Implemented close correctly #4002

Merged

Conversation

LarryOsterman
Copy link
Member

@LarryOsterman LarryOsterman commented Oct 6, 2022

Implement the Close() method correctly.

The cognitive services team reported that the Close() method with no parameters sent data to the server, which is an unexpected behavior. In addition, if you destroyed a WebSocket object without calling Close(), then the WebSocket codebase would AV. This fixes both of these issues.

Pull Request Checklist

Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:

See the detailed list in the contributing guide.

  • C++ Guidelines
  • Doxygen docs
  • Unit tests
  • No unwanted commits/changes
  • Descriptive title/description
    • PR is single purpose
    • Related issue listed
  • Comments in source
  • No typos
  • Update changelog
  • Not work-in-progress
  • External references or docs updated
  • Self review of PR done
  • Any breaking changes?

@LarryOsterman
Copy link
Member Author

Ping :). This fixes two of the issues the cognitive folks raised about the WebSocket functionality.

@LarryOsterman LarryOsterman merged commit b5dd9ef into Azure:feature/websockets Oct 11, 2022
@LarryOsterman LarryOsterman deleted the larryo/cognitivefixes branch October 11, 2022 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants