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

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

use unions in triton event messages

Right now all of the triton events are organized as flat structs rather than breaking them down into unions based on how the msg is being used at any given time.

We should follow the example of the swim protocol model to reduce event sizes and make it clearer which handlers are setting which fields.

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