Changes between Version 3 and Version 4 of WindowsFileSystemObserver
- Timestamp:
- 06/20/08 14:58:31 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WindowsFileSystemObserver
v3 v4 7 7 DFKI has got a developer license; the WindowsFileSystemObserver project is shipped with a free runtime license. 8 8 9 ---- 10 9 11 == Getting the code == 10 12 … … 14 16 }}} 15 17 18 ---- 19 16 20 == Starting == 17 21 18 22 You have 3 alternative ways of starting the file system observer: 19 23 * Start this batch file: [source:trunk/WindowsFileSystemObserver/Launch_WindowsFileSystemObserver.bat Launch_WindowsFileSystemObserver.bat] 24 * Use this launch configuration (from inside eclipse): [source:trunk/WindowsFileSystemObserver/WindowsFileSysObservation.launch WindowsFileSysObservation.launch] 20 25 * Start this main class as Java application (from inside eclipse): [source:trunk/WindowsFileSystemObserver/src/observer/de/dfki/km/filesysobservation/standalone/StandaloneWindowsFileSystemObservation.java StandaloneWindowsFileSystemObservation] 21 * Use this launch configuration (from inside eclipse): [source:trunk/WindowsFileSystemObserver/WindowsFileSysObservation.launch WindowsFileSysObservation.launch] 26 27 '''Attention:''' Make sure, that the [UserObservationHub] is running to receive file system observations! ;-) 28 29 ---- 22 30 23 31 == Configuring == … … 36 44 Alternatively, you can also invoke [{{{addFolderToObserve}}}]. 37 45 46 ---- 47 38 48 == Testing == 39 49 40 The file system observer creates NOPs of the observed file operations and passes them to the (hopefully running!) User Observation Hub.50 The file system observer creates NOPs of the observed file operations and passes them to the (hopefully running!) [UserObservationHub]. 41 51 42 52 Please keep in mind, that ALL file operations are observed and passed. That means: not only the file operations explicitly invoked by the user but also file operations done by the system or by applications are processed.