Persist message history #14

New Issue

jackhadrill · 2022-03-22T02:05:15Z

jackhadrill commented

2022-03-22 02:05:15 +00:00

This requires significant engineering to support synchronisation across multiple browser tabs.

Currently, multiple browser tabs do not pose a problem because each one acts as an isolated 'instance' of Mercury (with the exception of persisted settings).

Perhaps the message history should be stored to a 'session ID' and can selectively be loaded when the user opens a channel?

Need to work out how to prevent two tabs writing to the same session ID if this approach is selected.

This requires significant engineering to support synchronisation across multiple browser tabs. Currently, multiple browser tabs do not pose a problem because each one acts as an isolated 'instance' of Mercury (with the exception of persisted settings). Perhaps the message history should be stored to a 'session ID' and can selectively be loaded when the user opens a channel? Need to work out how to prevent two tabs writing to the same session ID if this approach is selected.

jackhadrill added the

enhancement

label 2022-03-22 02:05:15 +00:00

jackhadrill added this to the Mercury project 2022-03-22 02:05:15 +00:00

Sign in to join this conversation.