[wp-trac] [WordPress Trac] #64696: Real time collboration effectively disables persistent post caches while anyone edits a post

WordPress Trac noreply at wordpress.org
Thu Mar 12 23:24:51 UTC 2026


#64696: Real time collboration effectively disables persistent post caches while
anyone edits a post
--------------------------------------+--------------------------
 Reporter:  peterwilsoncc             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.0
Component:  Posts, Post Types         |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by czarate):

 There is another potential use case for this table that is distinct from
 the default HTTP polling provider: CRDT document persistence. Persisting
 the CRDT doc alongside the entity record (e.g., post) is essential for
 preventing the "initialization problem" where two peers have different
 initial state for their respective CRDT documents and therefore cannot
 apply updates consistently.

 Currently, we only persist CRDT documents for post entities, but that will
 change in the future as we sync additional entity types. CRDT documents
 for post entities are stored in post meta, but other entity types may not
 have an equivalent storage target (e.g., taxonomies, post types, etc.)
 Being able to persist CRDT documents in this new table (even when another
 sync provider is used) is appealing. It would simply be a row with a
 distinct type (`persisted_crdt_doc`).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64696#comment:61>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list