Skip to content

Refactor to allow multiple nodes #2

@jMyles

Description

@jMyles

Currently, the following barriers exist to administration of multiple nodes:

  • CJDNSAdminClient doesn't know or care which node is sending data to it. It has no way of distinguishing one node from another. It makes sense to instantiate a new CJDNSAdminClient for each node. If we do that, we then need to expose node information to the dispatch methods.
  • CirqueHendrixListener has no way to tell the frontend which node is calling. Perhaps we want different SockJS instances - one per node? Otherwise, we may want a different URL structure for each (ie, one NamedResource per node).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions