Hi, For the project I'm working on I need to distribute some zipped capnproto data. I'd like the data itself to be fairly small, but in particular I'd like the result of zipping it to be the smallest I can absolutely make it.
I used to use protocol buffers and implemented a size profiler for those. It basically traversed the entire structure while keeping track of the path that led to each point and counted the size of data encountered against a fixed-size suffix of the path. It was pretty simple but really useful in identifying where the problem points were. Now I've switched to capnproto and am considering doing the same for that, possibly as a stand-alone tool if I have time. I'm assuming it won't be all that hard to do with the reflection api. The plan then is to use it separately but in particular to combine it with a zip profiler I already have to find parts of the data that don't compress well. My question is, is this something anyone has already done or has thought about so they have any input into how such a tool should work? Also, I wonder if this is even something that might be useful to anyone else. c -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
