The one main issue I can think of regarding JSON is that we need to make sure we have a streaming parser, so that we don't need the entire thing in memory. We already have some memory issues with CPAN on just the highest-version index, and if we start pushing around all-version indexes this will just get worse.
Adam K On Wed, Jan 6, 2010 at 11:48 AM, David Golden <xda...@gmail.com> wrote: > On Tue, Jan 5, 2010 at 6:19 PM, Eric Wilhelm <enoba...@gmail.com> wrote: >> Given the constraint of bootstrap-ability, it seems like you should >> answer "Why not tsv?" before reaching for anything more complicated. > > Because META is already multi-dimensional and I don't want to find or > re-invent a wheel for representing multi-dimensional data in tsv. The > YAML/JSON debate is pretty much over as far as the META spec goes and > JSON wins. > > Thus, given the pending arrival of JSON into core for META, I see no > reason not to use JSON for index information as well. The last thing > we need is for CPAN/CPANPLUS/Tool-X to all implement their own tsv > parsers and we don't already have one in core, do we? (I could be > wrong there). > > This is such a stupid bikeshed conversation anyway. > > David >
