[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 peterwilsoncc):

 @ellatrix I had not (I was AFK for most of yesterday due to family
 commitments) but was simply focusing on why I thought it was a riskier
 change to alter the meta API than to add the new table. Both have risks
 attached, so it's a relative analysis.

 I'll drop a test on the PR with an example of the risk but my view remains
 that for the issue at hand the least risky option is to go with the new
 table.

 As RTC creates a lot of data, the custom table presents an additional
 advantage. As data increases a developer can simply(tm) truncate the new
 table if they wish to do a reset.

 I'm going to focus on @JoeFusco's PR for now as I think it offers the best
 chance of getting RTC in to core and Matt has already approved the new
 table to treat RTC as a first class object.

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