Mojom runtime type info: Use compression and base64 encoding.

Mojom runtime type info: Use compression and base64 encoding.

This change decreases the size of the data written into the generated source code that represents a serialized Mojo struct. Previously we were writing a literal array of bytes, written in decimal. Now we have done two things to decrease the size:
- We gzip the data
- We base64 encode the bytes and write an ascii string literal.
The result is that we decrease the size of the data written into the source by a factor of 30 in many cases.

BUG=#448
R=azani@chromium.org, zra@google.com

Committed: https://chromium.googlesource.com/external/mojo/+/2d4da54579bbcc2b37c28393fab8e3b25aee5e7f

[rudominer, 2016-03-10 18:16:35]

Patchset #1 (id:1) has been deleted

[rudominer, 2016-03-10 18:16:46]

Patchset #1 (id:20001) has been deleted

[rudominer, 2016-03-10 18:20:34]

Description was changed from

==========
Mojom runtime type info: Use compression and base64 encoding.

BUG=#448
==========

to

==========
Mojom runtime type info: Use compression and base64 encoding.

This change decreases the size of the data written into the generated source
code that represents a serialized Mojo struct. Previously we were writing a
literal array of bytes, written in decimal. Now we have done two things to
decrease the size:
- We gzip the data
- We base64 encode the bytes and write an ascii string literal.
The result is that we decrease the size of the data written into the source by a
factor of 30 in many cases.

BUG=#448
==========

[rudominer, 2016-03-10 18:24:17]

rudominer@chromium.org changed reviewers:
+ azani@chromium.org, zra@google.com

[rudominer, 2016-03-10 18:24:18]

Alex and Zach, ptal.

[zra, 2016-03-10 18:41:51]

lgtm!

Does this also fix the problem with the stability of the generated code?

[azani, 2016-03-10 20:51:54]

lgtm

[rudominer, 2016-03-10 20:58:24]

Description was changed from

==========
Mojom runtime type info: Use compression and base64 encoding.

This change decreases the size of the data written into the generated source
code that represents a serialized Mojo struct. Previously we were writing a
literal array of bytes, written in decimal. Now we have done two things to
decrease the size:
- We gzip the data
- We base64 encode the bytes and write an ascii string literal.
The result is that we decrease the size of the data written into the source by a
factor of 30 in many cases.

BUG=#448
==========

to

==========
Mojom runtime type info: Use compression and base64 encoding.

This change decreases the size of the data written into the generated source
code that represents a serialized Mojo struct. Previously we were writing a
literal array of bytes, written in decimal. Now we have done two things to
decrease the size:
- We gzip the data
- We base64 encode the bytes and write an ascii string literal.
The result is that we decrease the size of the data written into the source by a
factor of 30 in many cases.

BUG=#448
R=azani@chromium.org, zra@google.com

Committed:
https://chromium.googlesource.com/external/mojo/+/2d4da54579bbcc2b37c28393fab...
==========

[rudominer, 2016-03-10 20:58:26]

Committed patchset #2 (id:60001) manually as
2d4da54579bbcc2b37c28393fab8e3b25aee5e7f (presubmit successful).