Basically we receiver caps, and do an allocation query in order to influence the caps. Sebastien is asking if we can cache this query in order to pass this back without recursing when / if upstream makes an allocation query later. Note that this is a very tricky thing to cache, since download pipeline may have been changed meanwhile.

The following discussion from !436 (merged) should be addressed:

• @tpm started a discussion: (+12 comments)

  Is this the right or best fix? Doesn't this bypass the element entirely when upstream does an allocation query? Wouldn't it be better if the element could look at it on the way back to see if downstream supports the meta instead of doing its on query?