Developers

Release notes & Known issues

Release Notes



You can find here the latest Bolina’s release note, including what’s new and what has been fixed since the previous release. You’ll also find a repository of all release notes, in case you want to follow how our product has been developing.



Mobile: Android v0.9.39 (BETA) & iOS v0.9.30 (BETA) | Server: v0.9.51 (BETA)

Release date: April 13
Release versions: Mobile: Android v0.9.39 (BETA) & iOS v0.9.30 (BETA) | Server: v0.9.51 (BETA)

What’s new

Mobile
  • Automatically speed up any HTTP request
    • Few lines of code integration
    • Support most used Android HTTP clients:
      • Okhttp 2.7
      • Okhttp 3
      • HTTPUrlConnection
    • Any HTTP Server with no configuration required
      • NGINX
      • Apache
      • Your own
Protocol
  • Super fast protocol, high speed irrespective of latency and packet loss
  • The unique connection shared by multiple requests to the same Bolina Server, aka request multiplexing without the head-of-line blocking
  • Instant connection, 0-RTT enabled for all connections
  • End-to-end encryption in all bytes, with state of the art techniques:
      • stream cipher ChaCha20 for encryption
      • Poly1305 for message authentication
Codavel’s Private Area
  • Includes a dashboard to follow all performance metrics.
Others
  • Our Bolina Sample Project, a tool to help you see Bolina in action and evaluate its performance in just 30 minutes. It basically emulates different network conditions (namely packet loss and latency) to see how Bolina speeds up HTTP requests in a wide variety of scenarios. You can check it out here.

 

What has been fixed

This is our first release! That said, we would like to have all the feedback we can, in order to keep improving our product.

Please keep us posted of all the issues you might encounter and we will make our best to fix them, as fast as we can.

You can also access the full list of known issues here.



Known Issues



You can access the full list of known issues here. Since we are still in Beta version,  all feedback is super important. Please keep us posted of all the issues you might encounter and we will make our best to fix them, as fast as we can.

  • If you are running Bolina in a UDP blocked network, the bolina connection may not be established. In this case, Bolina SDK will automatically enable the fallback for all the requests with the possible performance penalty.
  • If you are running Bolina in a very low-end device, you may experience performance deterioration in scenarios with very high packet loss.
  • Occasionally, we detect a not yet completely identified behavior in the Bolina Client, which causes a significant increase on memory usage of Bolina Server. The memory returns to normal values as soon as the client closes the bolina connection.
  • Our aggressive stress tests to Bolina Server exposed some scarce crashes in edge cases, in which we are working on. As a workaround, we recommend using the option restart_always:true in the docker-compose.
  • We detected an issue causing a wrong calculation of Time To Live of the 0-RTT keys in the cache. This may lead to a key being valid for a longer period than expected, and consequently, a short increase of the memory used.
  • ECDSA certificates are not supported.
  • If you are trying to connect Bolina to a domain used in a previous successful connection by that Bolina Client, the key negotiation was completed with success and the previously shared key is not valid, you may experience a deterioration of performance caused by retransmission of some segments of data.
  • Rarely, our tests with multiple Bolina Clients doing multiple concurrent requests, show a few requests with response times much higher than the average of all others. Especially when the amount of data sent to the server is way larger than the data received from the server.
  • The HTTP connection between Bolina Server and Content Server is not using keep-alive, even when the HTTP header keep-alive is used. This is not critical since the connection between the Bolina Server and the Content Server is fast to establish – the latency between them is very low.
  • We detected a Bolina Server crash when the port in the “Host” HTTP header of the request, is not present or is wrong.
  • Canceling an HTTP request sent to Bolina may not work properly at all times. When it does not, it can cause some unnecessary data to be sent to Bolina Server.