Uploaded image for project: 'Fluid Infusion'
  1. Fluid Infusion
  2. FLUID-6511

Revise Nexus endpoints for /components/

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Nexus
    • Labels:
      None

      Description

      This issue combines two small revisions to the Nexus API (more of which are collected at this wiki page.

      Add a GET endpoint for /components/path.to.component

      Currently, WebSocket model bindings are the only way to get information about a component out of a Nexus "from the outside". The need for this functionality has come up in testing Nexus servers, but it may become necessary in use cases as well, and is nicely symmetrical with the GET endpoint for /defaults/.

      Construct components with PUT rather than POST

      Currently, the API endpoint for constructing a component is to send an HTTP POST request to the /components/{desired component path} . The traditional distinction between PUT and POST is that the former puts a resource at a requested location, while the latter determines the final location of the resource and sends it back to the requester. Component construction follows the former case, and should therefore use PUT.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ptcher Philip Tchernavskij
              Reporter:
              ptcher Philip Tchernavskij
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: