| rem | Index Level | remote-errors |
| Syntax |
remote-cache file.reference
remote-cache file.reference 0 remote-cache file.reference {number.of.updates} |
| Category | TCL |
| Type | Command |
| Description |
increases the performance of updates over a network by sending groups of updates at a time.
Normally, each update made on a remote file is sent immediately to the remote site. Because of limitations in network throughput, this can introduce performance delays in batch update applications. To alleviate this issue, batch updates can be cached and sent in groups. This significantly improves performance almost to the same point as a series of local updates. To turn on update-caching and/or to flush the cache, do "remote-cache file.reference" To turn off update-caching and to flush the cache, do "remote-cache file.reference 0" To set the number of updates to be cached before being sent, do "remote-cache file.reference number.of.updates". The higher the number.of.updates, the better performance will be. |
| Options | |
| See Also | |
| Example | |
| Warnings |
The user should be aware of the following warnings when using cached updates:
- Caching will not take place for binary items - Caching will not take place if any remote locks are held - The actual modification to the remote machine does not take place until the maximum number of updates fill the cache, the file is closed, a "remote-cache" command is executed for the file, the port drops to interractive TCL, or the port logs off. No other events flush the cache. - Because there may be a delay in referencing updated information, it is not valid to read from a remote file which has been updated through the cache unless the file is closed or "remote-cache" is executed. Note that executing "remote-cache" may be preferable because it reports success or failure in updating the remote machine. |
| Compatibility | D3 7.0 |
| rem | Index Level | remote-errors |