This may be related to the rq_vector issue that I opened. (I'm not entirely sure.) But another category of request that Thinknode had that was very useful was the 'meta' request. This was essentially:
template<class Value>
cradle::request<Value>
rq_meta(cradle::request<cradle::request<Value>>)
(Again, I'm being very loose with the request type. There would be more complicated templating involved in practice.)
Essentially, this takes a request that produces a request and then constructs a request to a) resolve the first request, and then b) resolve the request that that one produces.
(I'm not sure that rq_meta is actually the best name. Maybe rq_resolve?)
This may be related to the
rq_vectorissue that I opened. (I'm not entirely sure.) But another category of request that Thinknode had that was very useful was the 'meta' request. This was essentially:(Again, I'm being very loose with the
requesttype. There would be more complicated templating involved in practice.)Essentially, this takes a request that produces a request and then constructs a request to a) resolve the first request, and then b) resolve the request that that one produces.
(I'm not sure that
rq_metais actually the best name. Mayberq_resolve?)