You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
The RequestReply resource needs a data plane which:
Receives events
If the events has the replyAttribute set, splits the attribute and checks if the RequestReply resource has a matching event it should reply to, if it does -> send the event as a reply to that http request.
If the event does not have the replyAttribute set, add the id and signed id as the correlationId event attribute, and forward the event to the RequestReply's resolved brokerRef url
After the timeout for a request, reply with HTTP 408 Request Timeout if the event was not already replied to.
Exit Criteria
Unit tests of the data plane forwarding events to a test http server, and replying correctly. Unit tests of the data plane replying with 408 when the timeout occurs.
Time Estimate (optional):
How many developer-days do you think this may take to resolve? 2-3
Additional context (optional)
Add any other context about the feature request here.
Problem
The RequestReply resource needs a data plane which:
replyAttribute
set, splits the attribute and checks if the RequestReply resource has a matching event it should reply to, if it does -> send the event as a reply to that http request.replyAttribute
set, add theid
and signedid
as thecorrelationId
event attribute, and forward the event to the RequestReply's resolvedbrokerRef
urltimeout
for a request, reply with HTTP 408 Request Timeout if the event was not already replied to.Persona:
Which persona is this feature for?
Exit Criteria
Unit tests of the data plane forwarding events to a test http server, and replying correctly. Unit tests of the data plane replying with 408 when the timeout occurs.
Time Estimate (optional):
How many developer-days do you think this may take to resolve? 2-3
Additional context (optional)
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: