Added support for TCP_QUICKACK

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
networking

Research direction

Start with the dmSocket::SetQuickAck() API and trace the websocket socket lifecycle to determine where and when the flag is applied. Compare that behavior with the linked urllib3 reference; done means TCP_QUICKACK is enabled at the appropriate points on supported platforms and remains effective when the flag is reset.

Written by the indexing model from the issue text.

Description

There's now a function in the dmSDK (dmSocket::SetQuickAck()) that sets this flag on the supported platforms.

The question is where and when to call this function, since the flag seems to be reset every now and then.
E.g. according to this reference

Dominant language
C
Stars
51
Forks
17
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from defold/extension-websocket

All issues in defold/extension-websocket

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.