Ryan McCue
Ryan McCue
> ~2500 times get_item_schema was called That sounds like a bug; not sure how it's getting this many calls. How many posts per page is this for?
I dug into this issue; you're right that `get_item_schema` is scaling up linearly, and we can avoid that, but I'm not seeing it take up the majority of the call...
I wonder if this is a particular oddity in cachegrind, as I'm definitely not seeing this sort of time with the sampling method. Let's fix anyway.
> What is needed here? I'm interested in this ticket, would love to help if there's anything I can do. Best place to start is to design the data model...
> By the way, I worked with @danielbachhuber on a data model for Widgets for management via WP-CLI: wp-cli/wp-cli#728 The data serialization from WP-CLI can probably be taken almost wholesale,...
> Interesting. I think I like that better than what WordPress.com has done — more flexible. I like that fits pretty nicely with our envelope technique proposed in #507, but...
I'd say we might as well just wait until post-merge.
The code is primarily intended as a way for the client to differentiate between different responses, and additional information (IDs/etc) can be included in the data. This only really applies...
This runs into the same issue as last-modified: there's no real way to know when a post was changed in WordPress. For an ETag, we _may_ be able to do...
Agreed, we should error.