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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tcloud
  • capnet
  • Issues
  • #21

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

Convert membranes to a binary wrap rather than a wrap stack.

Currently, wrapped nodes store a stack of the membranes they are wrapped with, and are only unwrapped if they pass the opposite direction through the "top" membrane they are wrapped with. This leads to complexity and confusion when multiple wraps are added to an object.

Instead, we should just track which membranes an object is wrapped with irrespective of the order or count of those wraps. Wraps will only be added when the object has not yet been wrapped by that membrane.

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