Skip to content

rfc3: require request/response topic strings to follow service.endpoint form #424

@garlick

Description

@garlick

Problem: RFC 3 states that topic strings in request messages MAY include period delimiters", but for RPCs we have a convention of service.method that should be followed.

Since Flux services have implicit methods like disconnect, it probably makes sense to require there to be a distinct service and method component in request/response topic strings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No 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