FWIW, a zip file may not be a good format because the file index is just a O(n) access list (no matter how many sub-directories the zip file contains.) I didn't find any standard archive formats with O(log n) or better performance, which is why DrDr uses a custom format:
http://jeapostrophe.github.com/blog/2012/08/13/drdr-archive/ Jay On Wed, Oct 10, 2012 at 8:23 AM, Sam Tobin-Hochstadt <sa...@ccs.neu.edu> wrote: > On Wed, Oct 10, 2012 at 10:19 AM, Matthew Flatt <mfl...@cs.utah.edu> wrote: >> >> I guess we should try this, but I think we should keep it specific to >> bytecode loading. That is, I don't think we should try to splice a >> .zip-based filesystem into Racket's core filesystem operations. > > I would think that something along the lines of how classpaths work in > Java would be the right direction -- ie, PLTCOLLECTS could include > files (perhaps with a distinguished extension) in addition to > directories, and those would be ZIP files whose internal directory > structure was treated the way a directory entry directly in > PLTCOLLECTS is treated. > > -- > sam th > sa...@ccs.neu.edu > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev -- Jay McCarthy <j...@cs.byu.edu> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 _________________________ Racket Developers list: http://lists.racket-lang.org/dev
