Change mechanism of chapter locks
Change the architecture of chapter locking mechanism of Ketida.
Move from the current one way communication to full duplex via the use of websocket
cokoapps/server#19.
- Wax should establish a connection to the server via a
websocket
- When the above connection is unresponsive (heartbeat)/terminated the lock should be released.
- Info about the specific chapter id and the id of the user who has the lock should be exchanged on the initialization of the
websocket
- Counter measure of polling should be implemented (on
graphql
level) which will update periodically a timestamp for the lock - A
cron
job should be scheduled in order to scan for locks that have timestamps > than polling interval