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
The Steering Committee voted to accept this proposal. It was also confirmed by the Project Maintainer during the discussion that this proposal applies to all RPCs, and is trying to clarify that a Correlation ID should never be a duplicate from request to request. A request needs a response before a developer sends the same Correlation ID again in a new request.
The text was updated successfully, but these errors were encountered:
Proposal: Define Handling of Duplicate Correlation IDs
Review: smartdevicelink/sdl_evolution#476
Steering Committee Decision:
The text was updated successfully, but these errors were encountered: