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
At the same time, when sending a bunch of queries, the only way to detect all of them finishing is to wait for a GatewayResponse_Status with no active responders. This is error and race prone and does not allow for fully parallel querying either.
To solve this, add a top-level MsgID property to GatewayRequest and GatewayResponse that all clients fill in and can use on responses to multiplex responses back to the specific request that caused it. This can be a net-new addition and individual sdp protocol users (clients and servers) can start sending at processing this message id independently as long as they can handle empty IDs. Once everything is in plac, the client can make use of the new capability for finegrained request status processing.
The text was updated successfully, but these errors were encountered:
With the improved strictness of message-association in the sdp-go client, uncorrelated Error messages (e.g. when
query.Type == ""
in https://github.com/overmindtech/gateway/blob/09197e492f4cb5c99439dd33356308bf0aa46df0/gateway/request_session.go#L510-L517) have to abort all running requests, as there is no way to tag a specific query at the moment. Note that sdp-go doesn't abort either, instead hanging until the deadline!At the same time, when sending a bunch of queries, the only way to detect all of them finishing is to wait for a GatewayResponse_Status with no active responders. This is error and race prone and does not allow for fully parallel querying either.
To solve this, add a top-level
MsgID
property toGatewayRequest
andGatewayResponse
that all clients fill in and can use on responses to multiplex responses back to the specific request that caused it. This can be a net-new addition and individual sdp protocol users (clients and servers) can start sending at processing this message id independently as long as they can handle empty IDs. Once everything is in plac, the client can make use of the new capability for finegrained request status processing.The text was updated successfully, but these errors were encountered: