File: vfs_wrapper_fuchsia.h

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (27 lines) | stat: -rw-r--r-- 1,150 bytes parent folder | download | duplicates (11) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
 
// Copyright 2019 The Chromium Authors
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

#ifndef SQL_VFS_WRAPPER_FUCHSIA_H_
#define SQL_VFS_WRAPPER_FUCHSIA_H_

#include "third_party/sqlite/sqlite3.h"

namespace sql {

// Fuchsia doesn't provide a file locking mechanism like flock(). These
// functions are used to simulate file locking. On Fuchsia profile directories
// are not expected to be shared with other processes and therefore only one
// browser process may access sqlite files. These functions are designed to
// handle the case when the same sqlite database is open more than once from the
// same browser process. In most cases databases do not need to be open more
// than once, i.e. contention is expected to be rare, so the main goal of the
// design is simplicity and not performance. The manager maintains a list of all
// currently locked files.
int Lock(sqlite3_file* sqlite_file, int file_lock);
int Unlock(sqlite3_file* sqlite_file, int file_lock);
int CheckReservedLock(sqlite3_file* sqlite_file, int* result);

}  // namespace sql

#endif  // SQL_VFS_WRAPPER_FUCHSIA_H_