git-annex/Types/LockCache.hs

{- git-annex lock cache data types
 - 
 - Copyright 2014 Joey Hess <id@joeyh.name>
 -
 - Licensed under the GNU GPL version 3 or higher.
 -}

module Types.LockCache (
	LockCache,
	LockHandle
) where

import qualified Data.Map as M
import Utility.LockPool

type LockCache = M.Map FilePath LockHandle
use lock pools throughout git-annex The one exception is in Utility.Daemon. As long as a process only daemonizes once, which seems reasonable, and as long as it avoids calling checkDaemon once it's already running as a daemon, the fcntl locking gotchas won't be a problem there. Annex.LockFile has it's own separate lock pool layer, which has been renamed to LockCache. This is a persistent cache of locks that persist until closed. This is not quite done; lockContent stil needs to be converted. 2015-05-18 20:23:07 +00:00			`{- git-annex lock cache data types`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00			`-`
update my email address and homepage url 2015-01-21 16:50:09 +00:00			`- Copyright 2014 Joey Hess <id@joeyh.name>`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00			`-`
			`- Licensed under the GNU GPL version 3 or higher.`
			`-}`

use lock pools throughout git-annex The one exception is in Utility.Daemon. As long as a process only daemonizes once, which seems reasonable, and as long as it avoids calling checkDaemon once it's already running as a daemon, the fcntl locking gotchas won't be a problem there. Annex.LockFile has it's own separate lock pool layer, which has been renamed to LockCache. This is a persistent cache of locks that persist until closed. This is not quite done; lockContent stil needs to be converted. 2015-05-18 20:23:07 +00:00			`module Types.LockCache (`
			`LockCache,`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00			`LockHandle`
			`) where`

			`import qualified Data.Map as M`
use lock pools throughout git-annex The one exception is in Utility.Daemon. As long as a process only daemonizes once, which seems reasonable, and as long as it avoids calling checkDaemon once it's already running as a daemon, the fcntl locking gotchas won't be a problem there. Annex.LockFile has it's own separate lock pool layer, which has been renamed to LockCache. This is a persistent cache of locks that persist until closed. This is not quite done; lockContent stil needs to be converted. 2015-05-18 20:23:07 +00:00			`import Utility.LockPool`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00
use lock pools throughout git-annex The one exception is in Utility.Daemon. As long as a process only daemonizes once, which seems reasonable, and as long as it avoids calling checkDaemon once it's already running as a daemon, the fcntl locking gotchas won't be a problem there. Annex.LockFile has it's own separate lock pool layer, which has been renamed to LockCache. This is a persistent cache of locks that persist until closed. This is not quite done; lockContent stil needs to be converted. 2015-05-18 20:23:07 +00:00			`type LockCache = M.Map FilePath LockHandle`