You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
Should a provider return its mount prefix?
Providers use their own relative paths; the dispatcher restores the mount prefix.
- Caller /work/reportResolve mount→
- AFS dispatcherRemove prefix→
- Provider /report
Three views of one request
Suppose a provider is mounted at /work. The caller reads /work/report; the handler receives ctx.path = "/report". Its returned entry should still use /report. The dispatcher restores /work/report for the caller.
| Boundary | Path |
|---|---|
| Caller request | /work/report |
| Inside provider | /report |
| Provider result | /report |
| Caller result | /work/report |
If the provider adds /work itself, dispatch can add it again, producing /work/work/report. The mount root follows the same rule: /work outside corresponds to / inside.
Check more than read
List, search and query return collections of entries; each path follows the same boundary. A wrapper forwarding back into its host AFS may receive already-prefixed paths and must rebase them before returning outward.
Test the mount root, descendants and collections. Checking content alone misses a resource that can be read but cannot be referenced correctly afterwards.
Check your understanding
Should a provider return its mount prefix?
Providers use their own relative paths; the dispatcher restores the mount prefix.
Continue along a learning path
- Build and check a providerStep 1 of 6