« Previous - Version 9/17 (diff) - Next » - Current version
Panagiotis Kanavos, 05/24/2012 01:19 pm


Mapping of File Events to Actions

File System Events

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

  • Creation
  • Modification
  • Deletion
  • Move (also raised for renames)

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

Mappings

Local file events map to actions as follows:

File Event Local Exists Server Exists C==S(0) Network Action Local Action
Create / Change Yes No NA Upload Mark Normal
Yes Yes Skip Mark Normal
No Upload Mark Normal
No _ _ Skip Delete Entry
Delete _ Yes _ Trash Delete Entry
No _ Skip1 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(0) : Local file hash matches the current server hash
NA : Info not available
_ : Do not check