Lines Matching full:service
91 // The history service records page titles, and visit times, as well as
94 // This service is thread safe. Each request callback is invoked in the
112 // Initializes the history service, returning true on success. On false, do
127 // Unloads the backend without actually shutting down the history service.
137 // In practice, this will be called by the service manager (BrowserProcess)
139 // should be impossible for anybody else to call the service, even if it is
399 // is called when the history service has deleted the history.
418 // history service has created a new entry for a download in the history db.
424 // when the history service request is complete.
430 // history service has retrieved a list of all download state. The call
435 // history db. 'callback' runs when the history service request is complete,
445 // Called to update the history service about the current state of a download.
450 // Called to update the history service about the path of a download.
701 DCHECK(thread_) << "History service being called after cleanup";
717 DCHECK(thread_) << "History service being called after cleanup";
738 DCHECK(thread_) << "History service being called after cleanup";
761 DCHECK(thread_) << "History service being called after cleanup";
780 DCHECK(thread_) << "History service being called after cleanup";
789 DCHECK(thread_) << "History service being called after cleanup";
799 DCHECK(thread_) << "History service being called after cleanup";
811 DCHECK(thread_) << "History service being called after cleanup";
828 DCHECK(thread_) << "History service being called after cleanup";
840 // The thread used by the history service to run complicated operations.
