On 11/22/17, Joerg Sonnenberger <jo...@bec.de> wrote: > > (1) The need to parse all artifacts on clone. Artificates should be > strongly typed, i.e. the system should at the very least distinguish > fully between "content" blobs and "meta data" blobs. Only the latter > have and should be parsed.
That is a good point. I had already planned to do this, though for reasons other than what you propose. The fact that it reduces the amount of parsing work on a rebuild is a bonus that I had not previously thought of. > > (2) Store true differential manifests. I'm thinking that Fossil-NG will probably do like Git and store separate artifacts holding the content of each directory. (Git calls these "Tree Objects"). I need to do more research, but I'm thinking that for most check-ins, only one or two directory artifacts will actually change, even if there are dozens or hundreds (or multiple thousands as in NetBSD) of directory artifacts in a single check-out. > > (3) Make cluster manifests non-permanent artifacts. > I'm thinking of doing away with cluster artifacts entirely, and managing sync in some other way. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
