History log of /external/protobuf/java/src/main/java/com/google/protobuf/nano/CodedInputByteBufferNano.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
9b8022f792896f4a6831abe8e30ee5b7977a3677 23-Oct-2015 Nathan Mittler <nathanmittler@google.com> Minor cleanup in CodedInputByteBufferNano.

There is some cruft in the CodedInputByteBufferNano related to
fast/slow path for reading bytes that is not applicable for nano, due to
the fact that all of the data is buffered into a final byte
array. Cleaning up the code a bit to make it more explicit that
truncation will result if the data is not buffered.

Change-Id: I94c44e970790df0b9b6b598b8dfe1d510dd40bc0
/external/protobuf/java/src/main/java/com/google/protobuf/nano/CodedInputByteBufferNano.java
4f87f0d25b75e045f55cc09c8a9085c1cd7cb238 08-May-2015 Jeff Davidson <jpd@google.com> Add a flag to use offset/length with byte arrays.

This is an advanced option that most users won't want/need. However,
it can greatly optimize flows where we want to reuse byte[] buffers
from other locations without having to first copy the contents into
a new array of the exact correct size.

Bug: 20636336
Change-Id: Ia8d0af82e952858f9571f84110da621da776619c
/external/protobuf/java/src/main/java/com/google/protobuf/nano/CodedInputByteBufferNano.java
584381094c72fdeab18a7bb158c27da82b70aecd 04-May-2015 Andre Eisenbach <eisenbach@google.com> Handle 0-length byte buffers in micro and nano protobufs

Change-Id: I845ee1ab1005d25c8d77a8c2ed801c0f7b7c847b
/external/protobuf/java/src/main/java/com/google/protobuf/nano/CodedInputByteBufferNano.java
0e055f079f53b07de3705838a7b4742ce56839f8 19-Jun-2013 Brian Duff <bduff@google.com> Nano support for extensions and unknown fields.

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
/external/protobuf/java/src/main/java/com/google/protobuf/nano/CodedInputByteBufferNano.java
64d8d8f89050c5ada85341f967af391f4716a7cb 15-Mar-2013 Ulas Kirazci <ulas@google.com> Nano protobufs.

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
/external/protobuf/java/src/main/java/com/google/protobuf/nano/CodedInputByteBufferNano.java