Open main menu

Wikipedia β

Material Design logo for Google's implementation of the brotli file format specification.

Brotli is a data format specification[1] for data streams compressed with a specific combination of the general-purpose LZ77 lossless compression algorithm, Huffman coding and 2nd order context modelling. Brotli was initially developed to decrease the size of transmissions of WOFF2 web fonts, and in that context was a continuation of the development of zopfli, which is a zlib-compatible implementation of the standard gzip and deflate specifications. Although brotli (and zopfli) use the same compression and coding algorithm as gzip and deflate, brotli's newer data format allows a denser packing than the gzip and deflate data formats can. The brotli specification was generalized in September 2015 for HTTP stream compression (content-encoding type 'br'), and can now be used to encode any data sent by a web server to a web browser if both client and server support the format. This generalized iteration also improved the compression ratio by using a pre-defined dictionary of frequently-used words and phrases.

The brotli specification was developed in 2015–2016 by Google employees Jyrki Alakuijala and Zoltan Szabadka, and was accompanied by a reference implementation developed by the two authors of the specification together with Evgenii Kliuchnikov and Lode Vandevenne, who had previously developed Google's zopfli reimplementation of deflate/gzip compression formats in 2013.[2]:1 Unlike zopfli, which was a reimplementation of an existing data format specification, brotli was a new data format, and allowed the authors to improve compression ratios even further.[3]

Brotli was designed for use on a sequentially-processed data stream (a bitstream),[1]:2 rather than on discrete random-access files. This makes brotli particularly suitable for compressing data as it is sent over a network connection. Under ideal circumstances, this reduces the volume of data being transmitted. The transmission of a compressed stream may then also complete sooner than would be the case for an uncompressed stream, or a stream compressed with a less efficient stream compressor such as gzip or deflate. While gzip and deflate are comparatively light-weight compressors (i.e. less processor- and memory-intensive than brotli), and are already widely supported by many web servers, brotli has not yet been implemented as widely. The Brotli compressed data format was submitted to the Internet Engineering Task Force with a request for comment (RFC 7932) in July 2016.[1] The brotli data format is an integral part of the 2nd iteration of the Web Open Font Format.[1]:3

While Google's zopfli implementation of the deflate compression algorithm is named after a Swiss German word for a braided sweet bread and literally means "little plait", brotli is a Swiss German word for a bread roll and literally means "small bread".[3] Google's own implementation of the brotli specification was released under the terms of the permissive free software MIT license in 2016. A formal validation of the brotli specification was independently implemented by Mark Adler,cf. [1]:126 one of the co-authors of the zlib/gzip compression format and library. Adler's implementation was released under the terms of the similarly permissive Apache license.[4] Other implementations of the specification also exist, including one in the source-to-source haxe language.

Contents

AboutEdit

Brotli was first released in 2015 for off-line compression of web fonts.[5] The version of Brotli released in September 2015 by the Google software engineers contained enhancements in generic lossless data compression, with particular emphasis on use for HTTP compression. The encoder was partly rewritten, with the result that the compression ratio improved, both the encoder and the decoder have been sped up, the streaming API was improved, more compression quality levels have been added. Additionally, the new release shows performance improvements across platforms, with decoding memory reduction.[3]

Unlike most general purpose compression algorithms, Brotli uses a pre-defined 120 kilobyte dictionary, in addition to the dynamically populated ("sliding window") dictionary. The pre-defined dictionary contains over 13000 common words, phrases and other substrings derived from a large corpus of text and HTML documents.[6][2] Using a pre-defined dictionary has been shown to increase compression where a file mostly contains commonly-used words.[7]

Streams compressed with Brotli have the content encoding type "br".

Industry supportEdit

Browser supportEdit

  • Google Chrome has supported the 'br' content-encoding method since version 50 (released on 20 April 2016).[8]
  • Microsoft Edge has supported the 'br' content-encoding method since version 15 (released on 5 April 2017).[9]
  • Mozilla Firefox introduced support for the 'br' content-encoding method in version 44 (released on 26 January 2016).[10]
  • Opera has supported the 'br' content-encoding method since version 36,[8] but it was not enabled by default until version 38 (released 8 June 2016).
  • Safari has supported the 'br' content-encoding method since version 11 (released on 5 October 2017).

Web server supportEdit

  • For Apache HTTP Server, the 'br' content-encoding method has been supported by the mod_brotli module since version 2.4.26.[11]
  • Microsoft IIS has a IIS brotli community extension since March 2016 that adds support for the 'br' content-encoding method.
  • nginx has a ngx_brotli module provided by Google since December 2016.
  • Node.js has a community module called shrink-ray that adds support for the 'br' content-encoding method.
  • LiteSpeed Web Server has included the 'br' content-encoding method for static files only since version 5.2 in July 2017.
  • OpenLiteSpeed first introduced the 'br' content-encoding method for static files only in version 1.4.27 as part of the web server.

ReferencesEdit

  1. ^ a b c d e Alakuijala, Jyrki; Szabadka, Zoltan (2016), RFC 7932: Brotli Compressed Data Format, Internet Engineering Task Force Request for Comments, Fremont, CA: IETF Trust .
  2. ^ a b Alakuijala, Jyrki; Kliuchnikov, Evgenii; Szabadka, Zoltan; Vandevenne, Lode (22 September 2015), "Comparison of Brotli, Deflate, Zopfli, LZMA, LZHAM and Bzip2 Compression Algorithms" (PDF), The Comprehensive R Archive Network, r-project.org .
  3. ^ a b c Szabadka, Zoltan (September 22, 2015), "Introducing Brotli: a new compression algorithm for the internet", Google Open Source Blog, Mountain View, CA: opensource.googleblog.com .
  4. ^ Adler, Mark (Jan 26, 2015), "Brotli specification review and verification", Adler brotli, San Francisco: GitHub .
  5. ^ Sheeter, Rod (February 18, 2015), "Smaller Fonts with WOFF 2.0 and unicode-range", Google Open Source Blog, Mountain View, CA: opensource.googleblog.com .
  6. ^ Chirgwin, Richard (September 23, 2015), "Google's new squeeze: Brotli compression open-sourced", The Register, theregister.co.uk .
  7. ^ Larkin, Henry (2007), "Word Indexing for Mobile Device Data Representations", Proceedings of the 7th IEEE International Conference on Computer and Information Technology, IEEE .
  8. ^ a b Baheux, Kenji (15 January 2016), "Accept-encoding: br on HTTPS connection", Chrome Platform Status, chromestatus.com .
  9. ^ Trace, Rob (December 20, 2016), "Introducing Brotli compression in Microsoft Edge", Microft Edge Developer, blogs.windows.com 
  10. ^ Goodger, Ben; et al. (26 January 2016), "Firefox 44 release notes", Mozilla Firefox, Mozilla Foundation  .
  11. ^ "Changes with Apache 2.4.26", Apache HTTPD repository, svn.apache.org .
 -  Finley, Klint (22 September 2015), "Hooli, I Mean Google, Gives Away Compression Code for Free", Wired Online, wired.com .

External linksEdit