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

 @maxschmeling I would have liked to have been involved in that discussion
 (along with @czarate and @JoeFusco).

 As I mentioned earlier, the alternative approach is making some big
 changes to two fundamental WordPress APIs with very little architectural
 discussion: `WP_Query` (the most fundamental WordPress API) and the meta
 data APIs.

 I was able to demonstrate an edge case in some tests yesterday that will
 bypass the prevention queries that are intended to be prevented.

 A [https://veloria.dev/search/a4049126-d43f-4785-a58e-f51e52f18ce5 search
 of the plugin repo] for `meta_value` queries show that they are being used
 in pretty much all of the plugins in the highest levels of usage shown in
 the plugin repo.

 More significantly, I agree with @davidbaumwald's comment that post meta
 is the incorrect location to store the ephemeral data. With the existing
 WP Query/meta APIs it's very difficult to clear the post and post meta
 tables of expired data (it basically becomes irrelevant after a few
 hours).

 With the changes proposed to the WP Query/meta APIs it will become
 impossible to use these APIs to remove the ephemeral data as doing so
 requires querying by the very meta data that is being removed blocked from
 querying.

 > we definitely are going to want to continue to validate it for the 7.1
 cycle

 This concerns me most of all. Rushing changes to WP Query and the meta
 APIs for a situation that we're to reevaluate in a few short months is
 problematic. Given the choice, I'd rather allow the current issue on this
 ticket to remain than to make any changes.

 cc @matt, @matveb, @annezazu, @ellatrix, @griffbrad

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