Hi, all! Would this be even marginally useful: persistent sessions in fossil (i.e. cross-request data tied to a given login)?
The JSON bits i'm using include this support and it can use arbitrary storage back-ends via a generic interface. It would take all of about 20 or 30 minutes to put together an sqlite3 back-end for it. It can "sessionize" any data which can be JSONed, and we could re-use whatever login cookie fossil is using now for the session ID. Since the Blob class supports compression, we could also compress the session data. Is this something fossil could benefit from? i haven't found a good use case for it yet, but the bits are there anyway, so if someone can figure out a good use for it i'll get it plugged in. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
