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

Separate core API and API extensions #6

Open
danbim opened this issue Sep 8, 2011 · 0 comments
Open

Separate core API and API extensions #6

danbim opened this issue Sep 8, 2011 · 0 comments

Comments

@danbim
Copy link
Member

danbim commented Sep 8, 2011

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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant