Update LiveObjects docs for aggregate limits and notification mode#3264
Update LiveObjects docs for aggregate limits and notification mode#3264
Conversation
zknill
commented
Mar 11, 2026
- Clarify that the 6.5 MB object size limit is an aggregate across all objects on a channel, with no limit on object count
- Document the 64 KiB per-operation size constraint and that objects can grow beyond it via incremental updates
- Note that large objects may be split across multiple sync messages, affecting billing message counts
- Add documentation for the new 'notification' inband objects mode, which sends a REST API link instead of streaming full state
- Restructure inband-objects.mdx into 'objects mode' and 'notification mode' sections
- Fix limits.mdx description to say "aggregate size of all objects"
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip You can disable the changed files summary in the walkthrough.Disable the |
mschristensen
left a comment
There was a problem hiding this comment.
LGTM, although I'll leave @kaschula to review the inband objects changes
kaschula
left a comment
There was a problem hiding this comment.
Inband side looks good. I have an open PR with some inband changes which contains a few more details interms of examples and expected response formats. Go ahead and merge this I will rebase mine and add any extra bits.
4214e1b to
a7585c9
Compare
- Clarify that the 6.5 MB object size limit is an aggregate across all objects on a channel, with no limit on object count - Document the 64 KiB per-operation size constraint and that objects can grow beyond it via incremental updates - Note that large objects may be split across multiple sync messages, affecting billing message counts - Add documentation for the new 'notification' inband objects mode, which sends a REST API link instead of streaming full state - Restructure inband-objects.mdx into 'objects mode' and 'notification mode' sections - Fix limits.mdx description to say "aggregate size of all objects"
a7585c9 to
2e2ac11
Compare