Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
communications-backbone communications-backbone
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Communications Backbone System
  • communications-backbonecommunications-backbone
  • Issues
  • #53

Closed
Open
Created Jun 25, 2024 by Dan Jones@danjonOwner

Test creating a per-client recent cache using a stream queue

  • Implement per-client cache as stream queue
  • Using js adapter as an experiment
    • Set per message expiry like hydrogen
    • On reading from the inbox, set a per message type expiry and write back to cache
    • Use non-destructive read to get all recent history from queue
      • Is there a limit on the size of this either for storage or for reading - Wire up to hydrogen to replace local file cache
    • Test with multiple browser session to check cache can be retrieved many times
    • Test expired messages disapper
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking