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

[WordPress Trac]

#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):

 > Putting each client's awareness in its own row makes sense. What I don't
 understand with the current iteration is why we want `client_id` and
 `type` in the `update_value` blob. They're both necessary for filtering
 results, which we currently do by decoding every `update_value` blob and
 comparing on `type` and `client_id` in PHP.

 Both `client_id` and `type` are internal implementation details that are
 specific to Yjs and the polling provider. They could change in the future.
 Keeping the storage mechanism opaque to these implementation details
 greatly reduces the risk of breaking changes.

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