A JSON/REST interface sounds very promising. A few weeks ago I was playing around and tried creating a client-side file-browser treeview in HTML. What I ended up doing was getting the raw artifact (/raw/) and parsing it clientside. Not exactly perfect so I dropped it. A well designed JSON-interface would certainly have made my experiment easier. One thought: when the interface would rely on GET/POST it might create cross-domain problems when used from a web-browser. Therefore my vote goes to JSON(P) Jos
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
