Be-Bound

The Be-Bound Developer Hub

Welcome to the Be-Bound developer hub. You'll find comprehensive guides and documentation to help you start working with Be-Bound as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

BitBuffer

BitBuffer is a language/platform neutral data serialization algorithm designed by Be-Bound with two main objectives: optimize the efficiency of the data transmission and increasing significantly the ratio information/byte.

BitBuffer is embedded in Be-Bound Technology and relies on the Be-Bound Manifest to optimize the encoding and decoding of Messages.

This article presents the following:

  • An example of the Bitbuffer benefits.
  • A basic guide about how to use Bitbuffer.
  • When Bitbuffer is applied in Be-Bound Technology.

Performance

As shown in the below figures, BitBuffer optimizes the size of the exchanged data in comparison to their actual raw sizes.

Examples of encoded data using Be-Bound BitBuffer with corresponding sizes in bits/bytes

Examples of encoded data using Be-Bound BitBuffer with corresponding sizes in bits/bytes

Usage

BitBuffer requires:

  • Configuration file: BitBuffer is configured via a configuration XML file called Be-Bound Manifest. In this file, you determine which type of data structure you want to serialize and its characteristics. See more information here.
  • Data: BitBuffer doesn't accept encrypted data. The encryption has to be applied after the serialization process. This fact will have some implications described below.

Workflow

BitBuffer is automatically applied to each Message before their transmission. The serialization/deserialization doesn't require any additional action, and is automatically handled by Be-Bound SDK(s). See more information here

Serialization

The serialization process is applied in different points depending on the direction of the Message:

  • Messages from Device: the serialization process is applied when sending a Message through Be-Bound Android SDK.
  • Messages from Server:
    • If you are sending the Message with Be-Bound Server SDK, the serialization process is applied in Be-Bound Server SDK.
    • If you are sending the Message without Be-Bound Server SDK, the serialization process is applied in Be-Bound Proxy (E2EE not applicable).

Deserialization

The deserialization process is applied in different points depending on the direction of the Message:

  • Messages from Device:
    • If the Messages are delivered to a server using Be-Bound Server SDK, the deserialization process is performed by the Be-Bound Server SDK.
    • If you are sending the Message without Be-Bound Server SDK, the deserialization process is performed by the Be-Bound Proxy (E2EE not applicable).
  • Messages from Server: the deserialization process is performed by the Be-Bound Android SDK.

What's Next

Learn how to configure a Be-Bound Manifest

Getting started
Benefits of an optimal Be-App Manifest

BitBuffer


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.