[wp-trac] [WordPress Trac] #31436: Handle conflicts in concurrent Customizer sessions

[WordPress Trac]

#31436: Handle conflicts in concurrent Customizer sessions
--------------------------+-----------------------------
 Reporter:  westonruter   |       Owner:  westonruter
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  Future Release
Component:  Customize     |     Version:  3.4
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  javascript
--------------------------+-----------------------------
Changes (by westonruter):

 * owner:   => westonruter
 * status:  new => accepted


Comment:

 In regards to widgets, I've started hacking on a prototype for this. I'm
 trying out an implementation where a new post type is used for widget
 instances, allowing a widget ID to be derived from a post ID created at
 the time that the widget is added. This also has the benefit of widgets
 being versioned via post revisions, and also they could be drafted or
 scheduled. They're also much more scalable since all of the instance data
 is not crammed into a WP option as a serialized array. (I shudder to think
 what could happen on a site with Memcached Object Cache where widget
 instances of a given type grow larger than 1MB when serialized.)

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