Skip to content

[SDL 0162] Define Handling of Duplicate Correlation IDs #17

@theresalech

Description

@theresalech

Proposal: Define Handling of Duplicate Correlation IDs

This proposal is for the clarification of the SDL protocol behavior in the case that an app sends multiple messages with the same correlation ID.

Review: smartdevicelink/sdl_evolution#476

Steering Committee Decision:

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions