[wp-trac] [WordPress Trac] #43258: Output buffer template rendering and add filter for post-processing (e.g. caching, optimization)

[WordPress Trac]

#43258: Output buffer template rendering and add filter for post-processing (e.g.
caching, optimization)
-------------------------+--------------------------------
 Reporter:  nextendweb   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  General      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  docs, performance
-------------------------+--------------------------------

Comment (by dmsnell):

 One of the areas I want to explore with the HTML API is adding a new set
 of filters for final rendered content where we could scan the full HTML
 document on render and let plugins attach to different events on that
 scan. For example, one filter to give access to a tag and its attributes,
 another filter to process `#text` node content between tags.

 I'm optimistic that we'll be able to have something performant enough that
 if we can eliminate just a few of Core's existing filtering pipelines and
 replace them with this new single-pass transform that we'll break even on
 speed or even become faster than how things are today.

 There is a heap of code out there doing full parsing of the HTML available
 to the filter, which often runs slow or stresses the available memory. I'd
 like to better understand what kinds of needs are out there leading
 developers to enable output buffering.

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