Skip to Content

jibjib javame 1.4.2 compresses traffic

Since birdnest cannot be used in short period, I then implement compression to reduce traffic at the same threshold using gzip code backported from ttlite which is a fork of jibjib 1.0.17. Thanks!

As a result, 100 KB timeline could be compressed to 17 KB or less. Once jibjib supports OAuth through birdnest again, 20 KB response from birdnest would be reduced to 5 KB.

I wish to release stable version soon. But now beta is very stable and powerful.

Well, somehow compression

Well, somehow compression seems to be a bit flaky: there are times when a "full" update (50 tweets) get sent in ~5k but usually they are ~24k in size. Gateway is onedd (appspot gives back -1 size).

Gateway birdnest will reduce

Gateway birdnest will reduce size by omitting unused data. It is actually filtering more than compression.

You can use both filtering and compression for the best compression ratio.

Post new comment

The content of this field is kept private and will not be shown publicly.
Syndicate content