feat(realtime): introduce message-based protocol for subscriptions#2934
Conversation
- Added a new blog post detailing the transition to a single persistent WebSocket for Appwrite Realtime, allowing for incremental subscription changes without reconnecting. - Updated changelog to reflect the new Realtime features, including per-subscription lifecycle management and in-place updates. - Enhanced documentation across various SDKs to clarify subscription management and lifecycle handling. This update improves performance and usability for developers using Appwrite's Realtime features.
Greptile SummaryThis PR introduces a new blog post and changelog entry announcing the message-based Realtime protocol (single persistent WebSocket with incremental subscription changes), and updates the Realtime docs ( Confidence Score: 5/5Safe to merge — only documentation and blog content changes, no production code affected All findings are P2 style suggestions. The single inconsistency (missing No files require special attention beyond the one inline suggestion on the blog post Important Files Changed
Reviews (4): Last reviewed commit: "optimize" | Re-trigger Greptile |
Resolve Realtime docs conflicts: keep main subscribe/authentication pages, merge subscription-changes copy on the Realtime overview, and restore the intro sentence on subscribe about shared WebSocket and update/disconnect. Made-with: Cursor
…blog post and adjust cache configuration
Made-with: Cursor
This update improves performance and usability for developers using Appwrite's Realtime features.
What does this PR do?
(Provide a description of what this PR does.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)