1. 06 Sep, 2021 2 commits
  2. 02 Feb, 2021 2 commits
  3. 22 Jan, 2021 1 commit
  4. 11 Dec, 2020 1 commit
  5. 05 Sep, 2020 2 commits
    • Timo Koch's avatar
      Merge branch 'fix/client-specific-simulations-runs' into 'master' · ee07ab7a
      Timo Koch authored
      [backend][bugfix] Only communicate with client that requested simulation
      
      See merge request dumux-appl/dumux-web-app!35
      ee07ab7a
    • Timo Koch's avatar
      [backend][bugfix] Only communicate with client that requested simulation · 7510e3b9
      Timo Koch authored
      There is two versions of emit:
      (1) a context-aware version imported from flask_socketio
      (2) a context-ignorant version socketio.emit
      
      The (1) version automatically only communicates with the client
      that send the request. The (2) version is used in context-ignorant
      setting, e.g. a long-running background task like the Docker result
      streamer. However, the default will emit the message to all connected clients.
      So all clients get results from all currently running simulations.
      
      With this fix, we now pass the client/socket id to the stream which then only emits
      the result messages in the private "room" of the client that requested
      the simulation. In all other occassions in the backend, we use
      the context-aware version of emit now. Tested in local setup with two
      tabs in the same browser. Before this commit I would get messages
      from both running simulations. After this commit I only get the results
      of the simulation I started from that respective tab.
      7510e3b9
  6. 01 Sep, 2020 4 commits
  7. 31 Aug, 2020 17 commits
  8. 30 Aug, 2020 8 commits
  9. 27 Aug, 2020 1 commit
  10. 24 Aug, 2020 2 commits