Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • E eScriptorium
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • scripta
  • eScriptorium
  • Issues
  • #9

Closed
Open
Created Jan 24, 2019 by Robin Tissot@rtissotMaintainer

Offline process messages

The messages that tells the user a task is over are not saved in the message framework but sent directly though the opened websocket. If the user leaves the website the message will be lost. Check whether it's possible to tell if the message was received and if it wasn't add it to django's message framework. If it's not possible we need to find a way to check if the user is connected or not, beware that listing opened sockets is not recommended by channels because it is really inefficient so we may need to store opened connections another way (in redis ?).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking