Tue, 06 Jan 2015 21:39:09 +0100
Conditionally force memory storage according to privacy.thirdparty.isolate;
This solves Tor bug #9701, complying with disk avoidance documented in
https://www.torproject.org/projects/torbrowser/design/#disk-avoidance.
michael@0 | 1 | .. _data_reporting_service: |
michael@0 | 2 | |
michael@0 | 3 | ====================== |
michael@0 | 4 | Data Reporting Service |
michael@0 | 5 | ====================== |
michael@0 | 6 | |
michael@0 | 7 | ``/services/datareporting`` contains files related to an XPCOM service |
michael@0 | 8 | that collects and reports data within Gecko applications. |
michael@0 | 9 | |
michael@0 | 10 | The important files in this directory are: |
michael@0 | 11 | |
michael@0 | 12 | DataReportingService.js |
michael@0 | 13 | An XPCOM service that coordinates collection and reporting of data. |
michael@0 | 14 | |
michael@0 | 15 | policy.jsm |
michael@0 | 16 | A module containing the logic for coordinating and driving collection |
michael@0 | 17 | and upload of data. |
michael@0 | 18 | |
michael@0 | 19 | sessions.jsm |
michael@0 | 20 | Records Gecko application session history. This is loaded as part of |
michael@0 | 21 | the XPCOM service because it needs to capture state from very early in |
michael@0 | 22 | the application lifecycle. Bug 841561 tracks implementing this in C++. |
michael@0 | 23 | |
michael@0 | 24 | There is other code in the tree that collects and uploads data. The |
michael@0 | 25 | original intent of this directory and XPCOM service was to serve as a |
michael@0 | 26 | focal point for the coordination of all this activity so that it could |
michael@0 | 27 | all be done consistently and properly. This vision may or may not be fully |
michael@0 | 28 | realized. |