Lines Matching defs:ProfileIOData
48 // Conceptually speaking, the ProfileIOData represents data that lives on the IO
51 // implementation will maintain a reference to the ProfileIOData. The
52 // ProfileIOData will originally own a reference to the ChromeURLRequestContexts
54 // invoked, then ProfileIOData will release its reference to the
56 // reference to the ProfileIOData, so they exchange ownership. This is done
58 // ownership reversal prevents shutdown leaks. ProfileIOData will lazily
61 class ProfileIOData : public base::RefCountedThreadSafe<ProfileIOData> {
64 // they get called, from ProfileIOData owning ChromeURLRequestContext to vice
75 friend class base::RefCountedThreadSafe<ProfileIOData>;
82 // Setter is used to transfer ownership of the ProfileIOData to the context.
83 void set_profile_io_data(const ProfileIOData* profile_io_data) {
88 scoped_refptr<const ProfileIOData> profile_io_data_;
91 // Created on the UI thread, read on the IO thread during ProfileIOData lazy
124 explicit ProfileIOData(bool is_incognito);
125 virtual ~ProfileIOData();
130 // Lazy initializes the ProfileIOData object the first time a request context
170 explicit ResourceContext(const ProfileIOData* io_data);
176 const ProfileIOData* const io_data_;
183 // Does the actual initialization of the ProfileIOData subtype. Subtypes
194 // context from ProfileIOData to the URLRequestContextGetter.
205 // Data from the UI thread from the Profile, used to initialize ProfileIOData.
231 DISALLOW_COPY_AND_ASSIGN(ProfileIOData);
