| At line 1 changed 1 line. |
| !!! Clustering Support for ON Demand Read |
| !!! Clustering Support for "On Demand" Read |
| At line 4 changed 1 line. |
| !!! On Demand Read, as read only |
| !!! "On Demand" Read, as read only |
| At line 13 changed 1 line. |
| !!!On Demand read with delete |
| !!! "On Demand" read with delete |
| At line 17 changed 1 line. |
| !!!Archive option |
| !!! a) Archive option |
| At line 23 changed 1 line. |
| !!!Without Archive |
| !!! b) Without Archive |
| At line 29 added 1 line. |
| !!Note: Filelocks (java.nio.channels.FileLock) are used to synchronize access across nodes in the cluster |
| At line 31 added 17 lines. |
| {{{ |
| Platform dependencies |
| This file-locking API is intended to map directly to the native locking facility of the underlying operating system. Thus the locks held on a file should be visible |
| to all programs that have access to the file, regardless of the language in which those programs are written. |
| Whether or not a lock actually prevents another program from accessing the content of the locked region is system-dependent and therefore unspecified. |
| The native file-locking facilities of some systems are merely advisory, meaning that programs must cooperatively observe a known locking protocol in order to |
| guarantee data integrity. On other systems native file locks are mandatory, meaning that if one program locks a region of a file then other programs are actually |
| prevented from accessing that region in a way that would violate the lock. On yet other systems, whether native file locks are advisory or mandatory is |
| configurable on a per-file basis. To ensure consistent and correct behavior across platforms, it is strongly recommended that the locks provided by this API be |
| used as if they were advisory locks. |
| }}} |