Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • YARR YARR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 67
    • Issues 67
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • YARR
  • YARRYARR
  • Issues
  • #44

Closed
Open
Created Mar 27, 2020 by Bruce Joseph Gallop@bgallopMaintainer

RPC mechanism

There are many RPC (remote procedure call) mechanisms. The one implemented in devel_Distributed is based on jsonrpc, encoded in msgpack.

At least during development it should be possible to switch between implementations (CORBA, HTTP, DCOP etc (not real suggestions?) to enable evaluation of different options.

Assignee
Assign to
Time tracking