blob: ee6bbe3148ff321738908db4d564c9640a770d74 [file] [log] [blame]
[email protected]512d03f2012-06-26 01:06:061// Copyright (c) 2012 The Chromium Authors. All rights reserved.
[email protected]6faa0e0d2009-04-28 06:50:362// Use of this source code is governed by a BSD-style license that can be
3// found in the LICENSE file.
4
[email protected]6658ca82010-05-20 18:20:295#ifndef CHROME_COMMON_IMPORTANT_FILE_WRITER_H_
6#define CHROME_COMMON_IMPORTANT_FILE_WRITER_H_
[email protected]32b76ef2010-07-26 23:08:247#pragma once
[email protected]6faa0e0d2009-04-28 06:50:368
9#include <string>
10
11#include "base/basictypes.h"
12#include "base/file_path.h"
[email protected]3b63f8f42011-03-28 01:54:1513#include "base/memory/ref_counted.h"
[email protected]c9177502011-01-01 04:48:4914#include "base/threading/non_thread_safe.h"
[email protected]6faa0e0d2009-04-28 06:50:3615#include "base/time.h"
16#include "base/timer.h"
17
18namespace base {
[email protected]370bc732012-05-07 21:25:2019class MessageLoopProxy;
[email protected]6faa0e0d2009-04-28 06:50:3620class Thread;
[email protected]370bc732012-05-07 21:25:2021}
[email protected]6faa0e0d2009-04-28 06:50:3622
23// Helper to ensure that a file won't be corrupted by the write (for example on
24// application crash). Consider a naive way to save an important file F:
25//
26// 1. Open F for writing, truncating it.
27// 2. Write new data to F.
28//
29// It's good when it works, but it gets very bad if step 2. doesn't complete.
30// It can be caused by a crash, a computer hang, or a weird I/O error. And you
31// end up with a broken file.
32//
33// To be safe, we don't start with writing directly to F. Instead, we write to
34// to a temporary file. Only after that write is successful, we rename the
35// temporary file to target filename.
36//
37// If you want to know more about this approach and ext3/ext4 fsync issues, see
38// http://valhenson.livejournal.com/37921.html
[email protected]c9177502011-01-01 04:48:4939class ImportantFileWriter : public base::NonThreadSafe {
[email protected]6faa0e0d2009-04-28 06:50:3640 public:
[email protected]6c1164042009-05-08 14:41:0841 // Used by ScheduleSave to lazily provide the data to be saved. Allows us
42 // to also batch data serializations.
43 class DataSerializer {
44 public:
[email protected]6c1164042009-05-08 14:41:0845 // Should put serialized string in |data| and return true on successful
46 // serialization. Will be called on the same thread on which
47 // ImportantFileWriter has been created.
48 virtual bool SerializeData(std::string* data) = 0;
[email protected]512d03f2012-06-26 01:06:0649
50 protected:
51 virtual ~DataSerializer() {}
[email protected]6c1164042009-05-08 14:41:0852 };
53
[email protected]6faa0e0d2009-04-28 06:50:3654 // Initialize the writer.
[email protected]6fad2632009-11-02 05:59:3755 // |path| is the name of file to write.
[email protected]6658ca82010-05-20 18:20:2956 // |file_message_loop_proxy| is the MessageLoopProxy for a thread on which
57 // file I/O can be done.
[email protected]6faa0e0d2009-04-28 06:50:3658 // All non-const methods, ctor and dtor must be called on the same thread.
[email protected]6658ca82010-05-20 18:20:2959 ImportantFileWriter(const FilePath& path,
[email protected]370bc732012-05-07 21:25:2060 base::MessageLoopProxy* file_message_loop_proxy);
[email protected]6faa0e0d2009-04-28 06:50:3661
[email protected]6c1164042009-05-08 14:41:0862 // You have to ensure that there are no pending writes at the moment
63 // of destruction.
[email protected]6faa0e0d2009-04-28 06:50:3664 ~ImportantFileWriter();
65
[email protected]a83d42292010-08-17 22:51:1066 const FilePath& path() const { return path_; }
[email protected]6faa0e0d2009-04-28 06:50:3667
[email protected]6c1164042009-05-08 14:41:0868 // Returns true if there is a scheduled write pending which has not yet
69 // been started.
70 bool HasPendingWrite() const;
71
[email protected]6faa0e0d2009-04-28 06:50:3672 // Save |data| to target filename. Does not block. If there is a pending write
73 // scheduled by ScheduleWrite, it is cancelled.
74 void WriteNow(const std::string& data);
75
[email protected]6c1164042009-05-08 14:41:0876 // Schedule a save to target filename. Data will be serialized and saved
77 // to disk after the commit interval. If another ScheduleWrite is issued
78 // before that, only one serialization and write to disk will happen, and
79 // the most recent |serializer| will be used. This operation does not block.
80 // |serializer| should remain valid through the lifetime of
81 // ImportantFileWriter.
82 void ScheduleWrite(DataSerializer* serializer);
83
84 // Serialize data pending to be saved and execute write on backend thread.
85 void DoScheduledWrite();
[email protected]6faa0e0d2009-04-28 06:50:3686
87 base::TimeDelta commit_interval() const {
88 return commit_interval_;
89 }
90
91 void set_commit_interval(const base::TimeDelta& interval) {
92 commit_interval_ = interval;
93 }
94
95 private:
[email protected]6faa0e0d2009-04-28 06:50:3696 // Path being written to.
97 const FilePath path_;
98
[email protected]370bc732012-05-07 21:25:2099 // MessageLoopProxy for the thread on which file I/O can be done.
100 scoped_refptr<base::MessageLoopProxy> file_message_loop_proxy_;
[email protected]6658ca82010-05-20 18:20:29101
[email protected]6faa0e0d2009-04-28 06:50:36102 // Timer used to schedule commit after ScheduleWrite.
103 base::OneShotTimer<ImportantFileWriter> timer_;
104
[email protected]6c1164042009-05-08 14:41:08105 // Serializer which will provide the data to be saved.
106 DataSerializer* serializer_;
[email protected]6faa0e0d2009-04-28 06:50:36107
108 // Time delta after which scheduled data will be written to disk.
109 base::TimeDelta commit_interval_;
110
111 DISALLOW_COPY_AND_ASSIGN(ImportantFileWriter);
112};
113
[email protected]6658ca82010-05-20 18:20:29114#endif // CHROME_COMMON_IMPORTANT_FILE_WRITER_H_