On Fri, Jul 20, 2018 at 10:13 AM Florian Balmer <florian.bal...@gmail.com>

> I have created a (surprisingly simple) patch to attach a separate
> login cookie database (shared among all repositories in the same
> directory), so that plain login and logout actions will no longer
> cause repository database writes. With admin and user logs turned off,
> and "PRAGMA optimize" removed, the repository database is only touched
> if there's new contents, or new configuration settings.
> What's your comments to this? Does anybody care about the repository
> database, holding all your valuable contents, being modified
> frequently with simple non-contents state information?

This behaviour doesn't bother me at all (in 10 years of using Fossil), but
if a patch for working around it is simple and non-intrusive, i would
consider it to be an interesting feature (with the caveat that it might
impact future changes).

i conceptually like the idea of the login cookie/timestamps being in a
separate db, but i'm not sure that i like it enough to justify the idea of
maintaining two files where one file is sufficient. That wouldn't really
impact me much, as i keep all of my hosted .fsl files in one directory, but
for a hoster like chisselapp, where each repo is (probably) in its own
directory, it doubles the number of fossil-related files. One _potential_
problem i see, but it's largely hypothetical, is that the login cookie db
could become a point of locking contention if is used together with many
very active .fsl files. That is probably only possible if several of those
repos are _extremely_ active, though.

----- stephan beal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
fossil-users mailing list

Reply via email to