[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:  4.3
Component:  Customize     |     Version:  3.4
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  javascript
--------------------------+--------------------------

Comment (by adamsilverstein):

 Interesting proposal. I love the idea of heartbeat integration/locking!

 Can you elaborate on how individual settings locking would work? If two
 users are editing different settings at the same time and each try saving,
 wouldn’t the save of one user overwrite the others? Seems like this could
 lead to race conditions? Locking users out of customizer entirely would be
 much simpler to implement and might fulfil the goal of this ticket; it
 would certainly be a good start, although I agree that as the customizer
 is used more and more, individual settings locking would be useful.

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