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
  • #14

Closed
Open
Opened Jun 01, 2016 by Josh Kunz@joshkunzMaintainer

Add packet-loss handling

Right now, we assume no network loss of CapNet protocol packets. The protocol was designed to be tolerant to packet loss, but it's not yet implemented. We need to modify capnet.py to re-transmit packets when it thinks there has been a failure (as well as handle replies that come out of order). We also need to modify the CapNet controller to remember previous replies so they can be re-sent, and we need a strategy to deal with clearing this cache.

Unless there are objections, I plan on making the assumption that clients will only ever have a single pending request at a time, and we attempt to re-transmit until that request is satisfied.

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