Skip to content

Backport real-time collaboration peer limits from Gutenberg #75381#11266

Open
pkevan wants to merge 3 commits intoWordPress:trunkfrom
pkevan:pkevan/backport-gb-75381
Open

Backport real-time collaboration peer limits from Gutenberg #75381#11266
pkevan wants to merge 3 commits intoWordPress:trunkfrom
pkevan:pkevan/backport-gb-75381

Conversation

@pkevan
Copy link

@pkevan pkevan commented Mar 16, 2026

Description

Backport of Gutenberg PR #75381: Add per-room and per-user limits to enforce concurrent peer capacity during real-time collaboration. When a room reaches capacity (default: 2 peers), new users receive HTTP 429. Users can open multiple tabs up to a per-user limit (default: 2).

Two new filters allow customization:

  • real_time_collaboration_max_peers_per_room
  • real_time_collaboration_max_clients_per_user

Includes comprehensive test coverage for capacity enforcement, filter overrides, and edge cases.

Note: Client-side polling manager changes ship via Gutenberg @wordpress/sync package updates. This backport covers PHP server-side only.

Fixes #11120

Add per-room and per-user limits to enforce concurrent peer capacity
during real-time collaboration. When a room reaches capacity (default: 2
peers), new users receive HTTP 429. Users can open multiple tabs up to a
per-user limit (default: 2). Limits are configurable via filters:
- real_time_collaboration_max_peers_per_room
- real_time_collaboration_max_clients_per_user

Includes comprehensive test coverage for capacity enforcement, filter
overrides, and edge cases (existing users, disconnects, collection rooms).

PHP server-side backport only. Client-side polling manager changes ship
via Gutenberg @wordpress/sync package updates.

Fixes WordPress#11120
@github-actions
Copy link

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props paulkevan.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Tests for update counting and stale compaction use 4 client IDs from the
same user, which now exceeds the DEFAULT_MAX_CLIENTS_PER_USER limit of 2
introduced in the peer limits backport.
@pkevan pkevan force-pushed the pkevan/backport-gb-75381 branch from fb71fb0 to 3ab4056 Compare March 16, 2026 16:06
The empty() check was replacing null awareness (disconnect signal)
with default data, causing the peer limit disconnect test to fail.
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.

1 participant