Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • cameo cameo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CameoCameo
  • cameocameo
  • Issues
  • #36
Closed
Open
Issue created Nov 19, 2018 by yannick legoc@legocOwner

Optimise the opening and closing of sockets : redesign communication between apps

To optimise the sockets, it is better to define 1 socket REP per app so that only simple messages are sent. Do not block, the REP answers immediately as Acknowledge. It is simpler to implement the timeouts. The publisher and subscriber use this common message queue. A complete redesign is required. All sockets must have a lifetime greater than a simple request: sockets connected to server also live the time of the process.

Edited Nov 27, 2018 by yannick legoc
Assignee
Assign to
Time tracking