aboutsummaryrefslogtreecommitdiff
path: root/java/README.txt
diff options
context:
space:
mode:
authorWink Saville <wink@google.com>2014-03-22 01:09:34 +0000
committerGerrit Code Review <noreply-gerritcodereview@google.com>2014-03-22 01:09:34 +0000
commitdc2ab875690f8061ba1a712872133120792e4746 (patch)
treeaf51cf533d0eb2be7f0727982d2d48b88aa0b8bd /java/README.txt
parentddc98d6dd0800d180454b40ac9cc80f61cc53c21 (diff)
parentb7dd7d929443b774afe8d15d32a05c33bc8ad889 (diff)
downloadprotobuf-dc2ab875690f8061ba1a712872133120792e4746.tar.gz
protobuf-dc2ab875690f8061ba1a712872133120792e4746.tar.bz2
protobuf-dc2ab875690f8061ba1a712872133120792e4746.zip
Merge "Revert "Don't reset cachedSize to 0 in getSerializedSize""
Diffstat (limited to 'java/README.txt')
-rw-r--r--java/README.txt9
1 files changed, 0 insertions, 9 deletions
diff --git a/java/README.txt b/java/README.txt
index f958d147..13865f6d 100644
--- a/java/README.txt
+++ b/java/README.txt
@@ -437,15 +437,6 @@ and the runtime overhead. An overview of Nano features:
MessageNano.
- The 'bytes' type translates to the Java type byte[].
-The generated messages are not thread-safe for writes, but may be
-used simultaneously from multiple threads in a read-only manner.
-In other words, an appropriate synchronization mechanism (such as
-a ReadWriteLock) must be used to ensure that a message, its
-ancestors, and descendants are not accessed by any other threads
-while the message is being modified. Field reads, getter methods,
-toByteArray(...), writeTo(...), getCachedSize(), and
-getSerializedSize() are all considered read-only operations.
-
IMPORTANT: If you have fields with defaults and opt out of accessors
How fields with defaults are serialized has changed. Because we don't