Synnefo » Pithos MS Client

h1. Mapping of File Events to Actions

h2. File System Events

The File Agent raises the following events in response to local changes:

* Creation

* Modification

* Deletion

* Move (also raised for renames)

h2. Actions

The actions that can be performed in response to local events are:

* Upload the file

* Delete the file from the server

* Flag the file in Conflict

h2. Mappings

Local file events map to actions as follows:

|_.File Event        |_.Local File Exists   |_.Server File Exists|_.C==S  |_.Network Action|_.Local Action| 

|/4.Create / Change  |/3.Yes           | No            | NA        |Upload          |Mark Normal |

                                       |/2. Yes        | Yes       |Skip            |Mark Normal   |

                                                       | No        |Upload          |Mark Normal   |

                     |No               |_              |_          |Skip            |Delete Entry  |

|/2.Delete           |/2._             |Yes            |_          |Trash           |Delete Entry  |

                                       |No             |_          |Skip[1]         |Delete Entry  |

|Move                |_                |_              |_          |Rename          |Mark Normal, Rename Entry|

[1] The client always tries to move the server file to the Trash. If the file does not exist, the client ignores the 404 error, effectively skipping the file.

_Legend_

*C==S*     : Local actual file hash matches the current server hash

*NA*       : Info not available

*_*        : Do not check