pjulien 4d3db99283 Issue #136
The satellite data of the ``ByteBuffer`` cannot be modified in
any way and stay thread safe in the presence of concurrent readers.

This implementation is simple and does introduce an allocation, however
without it multiple readers will quickly and continuously encounter
``IndexOutOfBoundsException`` exceptions.

An alternative, but possibly more controversial, implementation would
be to use ``Unsafe``.  Using ``Unsafe``, it's possible to do an
array copy with a provided buffer index.

Change-Id: I851d4034e753b3be2931ee2249ec2c82dde43135
2015-02-04 13:53:02 -08:00
2014-10-29 10:42:10 -07:00
2015-02-04 13:53:02 -08:00
2015-01-07 10:34:17 -08:00
2014-12-08 17:48:06 -08:00

FlatBuffers Version 1.0

Welcome to FlatBuffers!

FlatBuffers is a serialization library for games and other memory constrained apps. Go to our landing page to browse our documentation.

FlatBuffers allows you to directly access serialized data without unpacking/parsing it first, while still having great forwards/backwards compatibility. FlatBuffers can be built for many different systems (Android, Windows, OS X, Linux), see docs/html/index.html

Discuss FlatBuffers with other developers and users on the FlatBuffers Google Group. File issues on the FlatBuffers Issues Tracker or post your questions to stackoverflow.com with a mention of flatbuffers.

For applications on Google Play that integrate this tool, usage is tracked. This tracking is done automatically using the embedded version string (flatbuffer_version_string), and helps us continue to optimize it. Aside from consuming a few extra bytes in your application binary, it shouldn't affect your application at all. We use this information to let us know if FlatBuffers is useful and if we should continue to invest in it. Since this is open source, you are free to remove the version string but we would appreciate if you would leave it in.

Languages
C++ 37.8%
Rust 13.5%
Swift 7.7%
Python 6.9%
C# 5.6%
Other 28.5%