How do src, bind and propBind differ?

Reading resources, writing input and updating properties are distinct connections.

One view displays a task title; another lets a person edit it. Both refer to a resource, but they require different operations.

Field	Responsibility	Question to ask
`src`	Read-only data connection	How does this node interpret the resource?
`bind`	Read–write input connection	Where does an edited value go?
`propBind`	Server-managed resource-to-property connection	Which property follows the resource?

Use all three connections in one task application:

A task list uses src to read tasks and show their titles and status.
A title input uses bind to read a title and write an edited value back.
The list also has a property—an interface setting—for how to sort. propBind can make that setting follow a resource containing the user’s sorting preference.

For example, the teaching mapping {"sort.field":"/example/preferences/task-sort"} reads the resource value into the sort.field property. If the value changes from title to status, the runtime sends the new property value to the renderer. This changes a list setting, not a task title. An application must still provide the example resource and nodes that support these fields.

These are distinct node contracts, not a promise that every node and renderer supports all three identically. A list and a media node can interpret source data differently.

Bindings do not bypass authorization. A visible input does not grant its caller permission to write the underlying resource.

Check your understanding

Which field should you examine to make a sort property follow a resource?

propBind, subject to support in the target runtime.

Continue along a learning path

From protocol to siteStep 3 of 9
Previous questionWhat is in an AUP tree?Next questionWhat happens after a click?

Further reading

Check your understanding

Continue along a learning path