Skip to content

Document what E1.31 behaviour is left to the application - #87

Open
stewartadam wants to merge 1 commit into
mainfrom
claude/project-thread-njq8b9-10-11-readme-scope
Open

stewartadam wants to merge 1 commit into
mainfrom
claude/project-thread-njq8b9-10-11-readme-scope

Conversation

@stewartadam

@stewartadam stewartadam commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Two E1.31-2016 behaviours depend on how the library is used, and the library leaves them to the caller. The compliance checklist in documentation/ already marks both as the user's job. This PR states that in the README so users don't assume the library handles them.

  • Transmission rate and keep-alive (§6.6.1, §6.6.2). SacnSource only transmits when send is called. The new section gives the refresh rate cap, the three repeats when data stops changing, the 800–1000 ms keep-alive interval, and the 2.5 s data loss timeout that receivers apply.
  • Priority and merging (§6.2.3). SacnReceiver::recv passes up unsynchronised data per source, with its priority and CID. The new section explains that arbitration and merging are the caller's job, and points to htp_dmx_merge and set_merge_fn.

Documentation only. There are no code changes.

SacnSource only transmits when send is called, and SacnReceiver passes
unsynchronised data up per source without arbitrating by priority. Say
so in the README, with what the standard expects (Sections 6.6 and
6.2.3) and the hooks the library provides.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KzaQVQThQpmqhvLapk99Vs
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