Hi again, As Richard mentioned earlier, the current fossil login mechanism does not tolerate a given user being logged in multiple times (each new login invalidates the previous one). While this almost certainly isn't a real limitation for the HTML interface, it will eventually become one for the JSON interface. e.g. i might have one applet for polling a timeline and another for polling tickets. That wouldn't work right now unless i force a re-login from each client (and can avoid the inevitable login/poll race condition between the two apps).
In a recent project of mine i have the same limitation of one login per user (because i don't want the db filling up with stale login state data) but i allow multiple logins for one user by recycling the login auth token values (analog to fossil's cookie value) if a user performs a login while a login is already active. The login op then always returns the same auth token for the given user/password until an explicit logout is performed (which clears the user.cookie value) or fossil cleans up the cookie because it expired (i don't know if it currently does any cookie cleaning but it does store the expiry time in user.cexpire). Would this modification be acceptable in fossil? i know it's a bit unconventional, but should be a fairly simple change to make with no backwards compatibility concerns (because fossil doesn't support multiple logins for one user right now). :-? -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
