summaryrefslogtreecommitdiffstats
path: root/java/src/main/java/com/google/protobuf/nano/CodedInputByteBufferNano.java
Commit message (Collapse)AuthorAgeFilesLines
* Handle 0-length byte buffers in micro and nano protobufsAndre Eisenbach2015-05-041-0/+2
| | | | Change-Id: I845ee1ab1005d25c8d77a8c2ed801c0f7b7c847b
* Nano support for extensions and unknown fields.Brian Duff2013-06-241-0/+17
| | | | | | | | | | | | | | | | | | | | You can use the processor option store_unknown_fields to switch this support on: aprotoc --javanano_out=store_unknown_fields=true:/tmp/out A separate option for extensions isn't required. Support for unknown fields must be turned on to allow storing and retrieving extensions, because they are just stored as unknown fields. If unknown fields are switched on, extension related code will be generated when a proto message includes an extension range, or an extension is encountered. By default, store_unknown_fields is false. No additional code is generated, and the generator will error out if protos contain extension ranges or extensions. Change-Id: I1e034c9e8f3305612953f72438189a7da6ed2167
* Nano protobufs.Ulas Kirazci2013-04-011-0/+624
Like micro protobufs except: - No setter/getter/hazzer functions. - Has state is not available. Outputs all fields != their default. - CodedInputStream can only take byte[] (not InputStream). - Repeated fields are in arrays, not ArrayList or Vector. - Unset messages/groups are null, not "defaultInstance()". - Required fields are always serialized. To use: - Link libprotobuf-java-2.3.0-nano runtime. - Use LOCAL_PROTOC_OPTIMIZE_TYPE := nano Change-Id: I7429015b3c5f7f38b7be01eb2d4927f7a9999c80