Skip to content
This repository was archived by the owner on Sep 21, 2022. It is now read-only.
This repository was archived by the owner on Sep 21, 2022. It is now read-only.

Separate core API and API extensions #6

@danbim

Description

@danbim

Design a mechanism to enhance a core API with an arbitrary set of API extensions. The core API should only contain the following primitive functionalities:

  • listen (add/remove controller)
  • send
  • reset
  • flash
  • check-alive
  • set-channel-pipeline
  • get-supported-channelhandlers

All other functionalities (such as the Node APIs virtualization features) should be accessible through some other Web service endpoint. The core API should therefore provide a method to discover the available API extensions which returns an extension self-description containing:

  • Name
  • Description
  • Version
  • URL to the WSDL file of the extension

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