AggregateRequest contains RequestMeta (which contains extra, common fields like serviceId) and a sequence of PartRequests (which describe the required parts)
An AggregateResponse is the output result version of an AggregateRequest
An AggregateResponse is the output result version of an AggregateRequest
It contains ResponseMeta and a sequence of PartResponses
ResponseMeta
PartResponse
Indicates that the response was explicitly forbidden from being stored
Indicates that the response must be validated
java timestamp, indicates until when the response can be used without validation
backend-defined String to be used for validation
a date. we do not parse it and use it as-is
Immutable wrapper for cookies
Immutable wrapper for cookies
Ideally we should handle no more than these fields
A request for a given part.
A request for a given part. One of more of these can be combined into a single AggregateRequest.
Note that if there is a "param" with a "body" key, it will be used as the Body of an Http Request if this part request has an Id that corresponds to an Http endpoint
String that corresponds to a dependency part Id
if set, will be passed to the corresponding response. Useful when an AggregateRequest contains several PartRequests with the same partId
list of parameters. Several parameters can have the same key; within those, order is kept as much a can be.
same as corresponding partRequest
same as corresponding partRequest
AggregateRequest contains RequestMeta (which contains extra, common fields like serviceId) and a sequence of PartRequests (which describe the required parts)
RequestMeta
List[PartRequest]