Section One BBS

Welcome, Guest.


Subject: Concurrent logins and data concurrency (last read msg pointers) Date: Mon Sep 05 2022 10:53 am
From: Matthew Asham To: All

Greetings!

New Synchronet operator here - used to run some boards back in the 90s and am re
ally happy to see Synchronet's longevity and open source model.

While testing my board (Synchronet 3.19c on Debian 11 / git 2458bfc3e336939c4893
a36007ad34bb11c646b2) I've noticed that if I am logged in via multiple nodes, my
 last message pointers don't seem to take affect on any other node that I'm logg
ed in to or if reading messages through other protocols such as NNTP.

eg:

user #1234 - login to node 1
user #1234 - login to node 2

user #1234 - read all messages on node 1 - no new messages are present
user #1234 - session on node 2 continues to see the messages as unread

This leads me to wonder whether it is safe to allow concurrent logins if data fo
r a session on node1 updates but the user has logged into another node performin
g work and if things like login time or other data might be overwritten when log
ging out.

What can I expect in terms of data consistency when a user is logged in via mult
iple services (NNTP/IMAP) or nodes?

Cheers

Matthew
--- SBBSecho 3.15-Linux
 * Origin: Reverse Polarity ~ Vancouver, Canada (1:153/149)
 ■ SynchronetVertrauen Home of Synchronet [vert/cvs/bbs].synchro.net

Previous Message       Next Message
Replies: Concurrent logins and data concurrency (last read msg pointers) (Digital Man)