Enhancement: can we get a copy of the documentation?
Really I wanted to put this into Issues as an enhancement request, but I couldn't figure out how... Would it be possible to take all the Developer Guide pages and put them in a tarball on the Downloads page? Or include them into the source tarball? Currently, one can only read the docs at google.com; having them on one's hard drive would come in handy when the development box has little or no internet access. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~--~~~~--~~--~--~---
Re: Protocol Buffers Vs. XML Fast Infoset
On Fri, Apr 10, 2009 at 5:24 AM, Alexander Philippou alexander.philip...@gmail.com wrote: The redundancy elimination mechanism of FI is actually a vocabulary and it works differently than compression algorithms do. I think we define compression differently. In my book, redundancy elimination and compression are pretty much synonymous. It sounds like you are using a more specific definition (LZW?). FI documents are good candidates for compression irrespective of whether a vocabulary is used or not. We've done a few tests with medium/large- sized documents and protobuf wasn't more compact than FI. Sure, but FI wasn't smaller than protobuf either, was it? I would expect that after applying some sort of LZW compression to *both* documents, they'd come out roughly the same size. (FI would probably have some overhead for self-description but for large documents that wouldn't matter.) Without the LZW applied, perhaps FI is smaller due to its redundancy elimination -- I still don't know enough about FI to really understand how it works. However, I suspect protobuf will be much faster to parse and encode, by virtue of being simpler. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~--~~~~--~~--~--~---
Re: Enhancement: can we get a copy of the documentation?
Using wget (a unix command -- available on Windows using Cygwin), you can download the whole site like so: wget -r -l inf -np -p -k http://code.google.com/apis/protocolbuffers/index.html Options: -r = Recursive -l inf = Infinite recursion depth -np = Don't follow links to parent directories -p = Fetch page prerequisites (images, stylesheets, etc., even if they are in parent directories) -k = Rewrite links (so that they work when viewing the documents locally) I ran this command, zipped up the contents, and placed them here: http://groups.google.com/group/protobuf/web/Protocol%20Buffers%20Documentation.zip On Fri, Apr 10, 2009 at 9:44 AM, Alexander Pensky apen...@gmail.com wrote: Really I wanted to put this into Issues as an enhancement request, but I couldn't figure out how... Would it be possible to take all the Developer Guide pages and put them in a tarball on the Downloads page? Or include them into the source tarball? Currently, one can only read the docs at google.com; having them on one's hard drive would come in handy when the development box has little or no internet access. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~--~~~~--~~--~--~---
Re: Enhancement: can we get a copy of the documentation?
Thanks much! I thought about wget, but I didn't want to scrape your website without asking first, it seemed kind of antisocial. :) On Apr 10, 3:51 pm, Kenton Varda ken...@google.com wrote: Using wget (a unix command -- available on Windows using Cygwin), you can download the whole site like so: wget -r -l inf -np -p -khttp://code.google.com/apis/protocolbuffers/index.html Options: -r = Recursive -l inf = Infinite recursion depth -np = Don't follow links to parent directories -p = Fetch page prerequisites (images, stylesheets, etc., even if they are in parent directories) -k = Rewrite links (so that they work when viewing the documents locally) I ran this command, zipped up the contents, and placed them here: http://groups.google.com/group/protobuf/web/Protocol%20Buffers%20Docu... On Fri, Apr 10, 2009 at 9:44 AM, Alexander Pensky apen...@gmail.com wrote: Really I wanted to put this into Issues as an enhancement request, but I couldn't figure out how... Would it be possible to take all the Developer Guide pages and put them in a tarball on the Downloads page? Or include them into the source tarball? Currently, one can only read the docs at google.com; having them on one's hard drive would come in handy when the development box has little or no internet access. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~--~~~~--~~--~--~---
