Nothing to add to the immediate discussion at this time. Just wanted to note that we have essentially the same problems to deal with in the BDB backend. The solution we've taken there is "don't drive public API callbacks from inside BDB transactions". It's not always the best for performance, but the FS API is such a high profile API for third-party consumers (very unlike the WC API in that respect, I'd imagine) that simplicity of the API "rules" was valued.
signature.asc
Description: OpenPGP digital signature
