Limits on retrying FileStore writes without duplicate data

Retrying FileStore writes

The org.eclipse.core.filesystem.FileStore API provides a putInfo method for writing data, but it does not expose any retry mechanism. When a write fails, a CoreException is thrown and the caller must decide how to recover. The API also offers no flag or contract that guarantees idempotency; if a retry is performed, the caller must manually ensure that duplicate data is not written.

In addition, the Job API can schedule background tasks that might be retried, and IResourceChangeListener events can detect failed writes, yet neither mechanism provides automatic duplicate suppression. Developers are left to implement their own idempotent logic.

Given this design, the following questions remain:

• What patterns or helper utilities exist in Eclipse to guarantee idempotent retries for FileStore writes?
• Is there a documented flag or parameter that can be added to putInfo or the Job API to prevent duplicate writes on retry?
• Would a future Eclipse release consider exposing a retryable write operation with built‑in duplicate suppression?