Eh, they're a marshaling format, we need an in-memory layout, and we might as well make the two the same.
On Fri, Dec 12, 2008 at 4:29 AM, Keunwoo Lee <[email protected]> wrote: > Protocol buffers are now open source. Why not use them as the storage > format? > > ~k > > On Mon, Dec 8, 2008 at 10:40 AM, Evan Martin <[email protected]> wrote: >> >> - Is the plan to mmap the data file directly? Avoids copies, but >> means we should (a) null terminate the string resources (maybe the rc >> format does this already) and (b) sort the resource entries by >> resource id for faster lookup. >> >> - We should make explicit the byte order for the int32s. We can't >> support non-x86 anyway because of v8 but it'd nice if it would at >> least error out during the build on big-endian platforms. >> >> - Do we care about compression? (Trading off disk accesses for CPU >> and memory.) Why not a zip file? >> >> On Mon, Dec 8, 2008 at 9:15 AM, <[email protected]> wrote: >> > >> > I wrote a short design doc about handling data resources and localized >> > strings on linux. >> > >> > >> > >> > http://sites.google.com/a/chromium.org/dev/developers/design-documents/linuxresourcesandlocalizedstrings >> > >> > Feedback welcome. >> > >> > tony >> > >> > > >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
