Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
C
capnet
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • tcloud
  • capnet
  • Issues
  • #20

Closed
Open
Opened Jul 27, 2016 by Josh Kunz@joshkunzMaintainer

Convert membranes from send/recv to wrap interface

Having membranes serve not only as wrapping/unwrapping objects, but also as message passing objects complicates the model needlessly. We should instead have membranes implement a generic wrap interface (which works differently depending on if they are internal or external membranes) that performs the wrapping procedure on objects.

To get the same effect as membrane send/recv, we just need to wrap an RP and have it behave normally.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tcloud/capnet#20