Skip to main content
Knowledge mapWhat should endure?ArcBlock

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

What should endure?

Follow the architectural questions behind the keynote.

This is a synthesis path for readers who understand the AFS foundations. It starts with X Window’s separation of responsibilities, then revisits addresses, operations, resource scope and presentation. Use the questions to examine which contracts a system change should preserve.

Along this path

  1. What did X Window teach us?

    Computation and the place where a person sees and controls it can be separated.

  2. What does a path give an agent?

    A path identifies a resource within a namespace, so operations can refer to it explicitly.

  3. Why do operation semantics matter?

    Naming a resource is useful only when consumers can understand what operations on it mean.

  4. Can the view change while the object stays the same?

    Separating context from projection lets multiple views refer to the same operational objects.

  5. Does shared context mean everyone sees everything?

    A Small World presents the resources relevant to one observer, rather than exposing the whole system.

  6. What makes separate parts composable?

    Compatible resource addresses and operations let parts cooperate without sharing every implementation detail.