2. The Frontiers handling of dispositions
Prev | A. Future changes in the API | Next

## 2. The Frontiers handling of dispositions

When the Frontier decides which URIs should be treated as deferred and which has failed, it must check the fetch status and have knowledge about every possible status code. This complicates adding new status codes. It should be possible to constrain the number of status groups the Frontier has to know and then let the processors decide which group a new status code falls into. Possible status groups are:

successful

failure

disregard

retry immediately

retry after any prerequisite

retry at some later time

Prev | Up | Next
1. The org.archive.util.HTTPRecorder class | Home | B. Version and Release Numbering