Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 694
    • Issues 694
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • briarbriar
  • Issues
  • #482

Closed
Open
Opened Jul 18, 2016 by akwizgran@akwizgranOwner

Store transport properties in metadata

Store the latest local and remote transport properties in metadata rather than iterating over all update messages whenever we need the latest properties.

Remote update messages can be deleted as soon as the properties have been extracted. When message receipt hooks have been implemented (#481), local update messages can be deleted as soon as the contact has received them.

Assignee
Assign to
Android 1.0
Milestone
Android 1.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#482