Concurrent invocations of touch() or set() for the same session id can result in problems. (See isssue 88).
Practically, this may happen when a browser concurrently loads multiple resources for the same site/page.
The problem may be limited to projects backed by an SQLite db, but this has not yet been carefully tested; prisma or express-session may alternately / additionally be implicated.
As a work-around for now, this PR dis-allows concurrent calls to touch() or set() for the same session id by default - but provides options to over-ride this new behavior, in case there happen to be scenarios for which the "fix" proves more problematic than helpful.
Concurrent invocations of
touch()
orset()
for the same sessionid
can result in problems. (See isssue 88).Practically, this may happen when a browser concurrently loads multiple resources for the same site/page.
The problem may be limited to projects backed by an SQLite db, but this has not yet been carefully tested;
prisma
orexpress-session
may alternately / additionally be implicated.As a work-around for now, this PR dis-allows concurrent calls to
touch()
orset()
for the same sessionid
by default - but provides options to over-ride this new behavior, in case there happen to be scenarios for which the "fix" proves more problematic than helpful.