<h1 id="tuiter-011">Tuiter 0.1.1</h1>
<p>I've been working on <a href="https://github.com/danzajdband/Tuiter">Tuiter</a>. This new release count with two major features: <strong>Automatic Reconnection</strong> and <strong>Gzip compression</strong>.</p>
<h2 id="automatic-reconnection">Automatic Reconnection</h2>
<p>Streaming API connections are incredible powerful and it's very common to keep those connections open all the time. The thing is <a href="https://dev.twitter.com/docs/streaming-api/concepts#connecting">Twitter closes valid connections</a> very often because of:</p>
<ul>
<li>Duplicate clients logins (earlier connections terminated)</li>
<li>Hosebird server restarts (code deploys)</li>
<li>Lagging connection terminated (client too slow, or insufficient bandwidth)</li>
<li>General Twitter network maintenance (Load balancer restarts, network reconfigurations, other very very rare events)</li>
</ul>
<p>Following the Twitter Team recommendations I made this simple <em>Automatic reconnector</em> for the library.</p>
<h4 id="gzip-compression">Gzip compression</h4>
<p>Twitter give us the oportunity of reduce the streams to 1/5 size using <a href="https://dev.twitter.com/docs/streaming-api/concepts#gzip-compression">Gzip-formatted data</a> via <code>Accept-encoding</code> header. Using the header and uncompressing with the help of the node.js core module 'zlib' now all API calls are performed with this format.</p>
<h2 id="state-of-the-art">State of the art</h2>
<p>For the next release I want to improve the performance of the library and the parameters pre-processing. Don't forget to <a href="https://github.com/danzajdband/Tuiter">Fork me on Github!</a></p>

---
path: tuiter-0-1-1
tag: node.js, tuiter
---

# Tuiter 0.1.1

I've been working on [Tuiter](https://github.com/danzajdband/Tuiter). This new release count with two major features: **Automatic Reconnection** and **Gzip compression**.

## Automatic Reconnection

Streaming API connections are incredible powerful and it's very common to keep those connections open all the time. The thing is [Twitter closes valid connections](https://dev.twitter.com/docs/streaming-api/concepts#connecting) very often because of:

  * Duplicate clients logins (earlier connections terminated)
  * Hosebird server restarts (code deploys)
  * Lagging connection terminated (client too slow, or insufficient bandwidth)
  * General Twitter network maintenance (Load balancer restarts, network reconfigurations, other very very rare events)

Following the Twitter Team recommendations I made this simple _Automatic reconnector_ for the library.

#### Gzip compression

Twitter give us the oportunity of reduce the streams to 1/5 size using [Gzip-formatted data](https://dev.twitter.com/docs/streaming-api/concepts#gzip-compression) via `Accept-encoding` header. Using the header and uncompressing with the help of the node.js core module 'zlib' now all API calls are performed with this format.

## State of the art

For the next release I want to improve the performance of the library and the parameters pre-processing. Don't forget to [Fork me on Github!](https://github.com/danzajdband/Tuiter)