willscott
commented
3 years ago This is a good question. I imagine most transport-specific options would be preferably specified in the constructor to the transport, rather than at the content-routing fetch time.
I think we could imagine in the scope of one call to ask for:
- hints about the selector that is triggering the request, or the parent cid that this one is downstream of
- relative priority of the request (e.g. 'don't open new network requests for this one')
out of interest, what kinds of options might one expect to be passed here? or are we defining a consistent interface that's going to be copied for other transports and therefore expect a lot of option-chatter?