Hi, fossilers, i'm working on my json library (the one i used to add JSON output to the fossil timeline with) and just implemented a feature which gave me some food for thought vis-a-vis fossil... persistent sessions. As of an hour or so ago i've got a small, JSON-based session management system which can use files, sqlite3, or mysql as storage. By "session" i basically mean a JSON object tree which clients interact with using a relatively high-level OO interface. They're persistent in that they use an HTTP cookie to track a session ID, and store/restore the JSON tree to/from the specified storage (configured via a JSON file).
Are there areas of fossil's ui which would benefit from having sessions? i can't personally think of any, but maybe some inventive user out there can think of a couple. -- ----- 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
