Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 // Copyright 2015 The Chromium Authors. All rights reserved. | |
| 2 // Use of this source code is governed by a BSD-style license that can be | |
| 3 // found in the LICENSE file. | |
| 4 | |
| 5 // Package bundler exports the Bundler interface and its implementation, as well | |
| 6 // as supporting interfaces. | |
| 7 // | |
| 8 // A Bundler is responsible for efficiently buffering and clustering LogDog | |
| 9 // Butler protobufs together for output. It primarily focused on two protobufs: | |
|
tandrii(chromium)
2015/08/11 18:31:05
nit: It *is* primarily...
dnj (Google)
2015/08/12 03:20:09
Done.
dnj
2015/09/02 01:58:14
Done.
| |
| 10 // - The ButlerLogBundle_Entry, which represents a series of logs and | |
| 11 // metadata belongining to a single stream. | |
|
tandrii(chromium)
2015/08/11 18:31:05
s/belongining/belonging
dnj (Google)
2015/08/12 03:20:09
Done.
dnj
2015/09/02 01:58:14
Done.
| |
| 12 // - The LogEntry, which is a single chunk of unqualified log data. | |
| 13 // | |
| 14 // These protobufs comprise log data, and are grouped together for export in | |
| 15 // a ButlerLogBundle protobuf. | |
| 16 // | |
| 17 // A ButlerLogBundle_Entry will be exported if it matches ANY of the following | |
| 18 // conditions: | |
| 19 // - It has attached log data. | |
| 20 // - It has terminal information. | |
| 21 // | |
| 22 // Since LogDog outputs can be size-constrained, the Bundler tracks the expected | |
| 23 // aggregate buffered protobuf size and, on export, breaks the buffered | |
| 24 // protobufs into bundles along a size threshold boundary. | |
| 25 package bundler | |
| OLD | NEW |