microsoft / microsoft/Windows-classic-samples
WinhttpWebsocket.cpp blocking when server doesn't send messages
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
Thank you for providing the example WinhttpWebsocket.cpp However, if the server side takes a long time to respond or hangs without responding for hours, the connect stay blocked. Is it possible to come out of the blocking lets say a configurable 30 seconds, so that the client can go back and wait to receive data or close connection?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading Samples/WinhttpWebsocket/cpp/WinhttpWebsocket.cpp and run the sample against a server that does not send messages. Trace where the client remains blocked while waiting for the server, then verify that a configurable timeout lets it resume waiting or close the connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100