WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #28580, comment 27


Ignore:
Timestamp:
03/14/2016 09:35:37 PM (4 years ago)
Author:
westonruter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28580, comment 27

    initial v1  
    1 Lazy-loading widgets have some special performance considerations of their own. At the moment, when a pre-existing widget is instantiated dynamically, an `update-widget` Ajax request is kicked off to obtain the rendered form. This issue will be irrelevant to JS-driven widgets(#33507), when they are implemented, because the widget control will be constructed entirely client-side from a JS template. For legacy widgets that aren't JS-driven, we should batch together the `update-widget` Ajax calls (similar to how selective refresh requests are now batched in 4.5) to prevent slamming the server with dozens (or hundreds) of HTTP requests for (very) large sidebars.
     1Lazy-loading widgets have some special performance considerations of their own. At the moment, when a pre-existing widget is instantiated dynamically, an `update-widget` Ajax request is kicked off to obtain the rendered form. This issue will be irrelevant to JS-driven widgets (#33507), when they are implemented, because the widget control will be constructed entirely client-side from a JS template. For legacy widgets that aren't JS-driven, we should batch together the `update-widget` Ajax calls (similar to how selective refresh requests are now batched in 4.5) to prevent slamming the server with dozens (or hundreds) of HTTP requests for (very) large sidebars.