[wp-trac] [WordPress Trac] #37181: Use metadata api in *_network_options

[WordPress Trac]

#37181: Use metadata api in *_network_options
--------------------------------+-------------------------------------
 Reporter:  spacedmonkey        |       Owner:  spacedmonkey
     Type:  enhancement         |      Status:  reopened
 Priority:  normal              |   Milestone:  6.2
Component:  Networks and Sites  |     Version:  4.4
 Severity:  normal              |  Resolution:
 Keywords:  ms-roadmap          |     Focuses:  multisite, performance
--------------------------------+-------------------------------------
Changes (by desrosj):

 * keywords:  ms-roadmap revert => ms-roadmap
 * milestone:  6.1 => 6.2


Comment:

 The dev note has been updated to include a callout at the top.

 Since the 6.1 aspects of this have been addressed, I'm going to leave this
 open punt to 6.2. There was agreement that this could still be beneficial
 and deserves further exploration, but would need other related problems to
 be solved at the same time to be feasible.

 Just to bring some thoughts @johnjamesjacoby shared that summarize a great
 path forward over from Slack for easier reference:

 > Hello! I’m onboard with reverting for 6.1, and suggest:
 > - keeping it open
 > - moving to the 6.2 milestone
 > - landing it simultaneously with some future meta data cache key
 improvement to address the forever-old 1MB memcached issue
 > The major (future) benefit of getting network options using the meta
 data API is it inherits all improvements from it (in addition to removing
 the bespoke cache-key implementation of options)
 >
 > Would love to see (and participate in) a collaborative effort from
 cache, options, meta, multisite, & performance contributors (of which
 there is some overlap) to identify, document, and make progress on a
 roadmap.

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