Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
codes
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • codes
  • codes
  • Issues
  • #116

Closed
Open
Opened Jan 14, 2016 by Jonathan Jenkins@jenkins
  • Report abuse
Report abuse

generalize RPC-like workflow

Just putting this here before I forget...

There are numerous cases in our models which we have an RPC-like event flow (execute event on server with x,y,z parameters, and when it is finished send back to me a completion event with a,b,c output parameters). It may be worth thinking how we can generalize this concept. The concept has overlaps with the message funneling currently used in LSM/modelnet/resource models, the tw_memory feature, and #28 (closed).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
CODES task
Assign labels
  • View project labels
Reference: codes/codes#116