Author: Darth Autocrat

This is an optional container of arbitrary data that can be added to a FetchReplyData. This data is meant to be logged, but not sent back in a fetch reply (it should be added after the reply is prepared). Use FetchResponsePreparatorImpl::AddTrawlerPrivateDataToFetchReplyData to add. See also the comment in fetch_response_preparator_impl.cc. Next Tag: 49

Information about provenance of a result support.

Wire-format for a Status object

Proto message containing the id, localized title, score, and hierarchy level of a trusted genome entity. Next ID: 12

Proto message containing policy related information.

ClientServiceInfo is meant for trawler/harpoon clients which are in turn services to store some data specific to their clients. E.g., Kodachrome may serve multiple other clients. In this case they can store their client name here. Webmirror may also store the feed name here even though a feed is technically not a service client. ClientServiceInfo is in nature similar to ClientInfo, except it’s stored in FetchReplyData (i.e., trawler logs), whereas ClientInfo is copied to FetchReply (outside FetchReplyData), thus it’s not stored in trawler logs.

===================== Beginning of Deprecated Part ======================

This is similar to CrawlDates group in FetchReplyData, except that 1) it’s a message; 2) it’s filled in each Redirects hop; and 3) the timestamps are in ms rather than seconds since Unix Epoch.