Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N
nrm
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • argo
  • nrm
  • Issues
  • #14

Closed
Open
Opened Sep 06, 2018 by Swann Perarnau@perarnau
  • Report abuse
  • New issue
Report abuse New issue

Change Upstream API messaging layer

The upstream API relies on the daemon being a subscriber to upstream commands. Zeromq doesn't exactly recommends these kinds of setups, with a stable component being subscriber, and ephemeral components being publishers. Different implementations of zmq will also break in subtle ways on this pattern.

The proper solution is to change this part of the upstream API to a REQ/REP pattern. This way the commands can be acknowledged. One thing that needs to be discussed for that is which replies to send on the pub socket and which send as a reply.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: argo/nrm#14