Bug #3754
Impacts of sd:dependency unclear
| Status: | New | Start date: | 2010-10-19 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - |
Description
5.3.2. Collection Feed
This is pretty unclear to me.Through one or more share:dependency elements the collection feed can optionally declare dependencies on other collection feeds from this or other servers that should be recursively processed before the current one.
- Algorithm?
- What does sd:dependency mean for processing snapshots/fragments? Must a client contact all sd:dependencies in advance?
History
Updated by Graham Moore over 1 year ago
The spec is not clear. Here is what it means :)
For each action you are about to perform wrt syncing a given collection you should first carry out that operation on each of the listed dependent collections.
e.g. going to grab latest snapshot, then grab the latest snapshot from all dependencies first.
Topic Maps Lab