Skip to main content
Knowledge mapFrom finding a resource to operating it reliablyArcBlock

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← AFS and interfaces

Learning path

From finding a resource to operating it reliably

Distinguish addresses, capabilities, updates and failures in a shared working environment.

This path is for readers who understand that AFS addresses resources by path and want to understand their actual behavior. It does not require AUP knowledge or begin with writing code.

Follow report and poll examples through entry points, supported operations, updates reaching another display, stale edits, two ways to find content and responses to failure.

By the end, you should be able to explain why a shared address is a starting point for working together, rather than a guarantee of live synchronization, unrestricted writes or automatic conflict resolution.

Along this path

  1. Where does a mount put a resource?

    An entry path and the resource’s original location are different things.

  2. Does an address tell you what you can do?

    Location, supported operations and caller authority are separate questions.

  3. How does another display learn about a change?

    Reading the same address and receiving changes are separate steps.

  4. What happens when two people edit at once?

    A shared address does not decide how stale edits are handled.

  5. Why distinguish search from query?

    Finding relevant content differs from selecting records by explicit conditions.

  6. Should a failed operation be retried or handled differently?

    Missing, unsupported, denied and conflicting operations need different responses.