Difference between revisions of "Granule Acceptance"
| Line 8: | Line 8: | ||
The first default criterium: granules are not normally accepted twice by the same adapter. | The first default criterium: granules are not normally accepted twice by the same adapter. | ||
| + | |||
| + | In some of the more complex personalities, you might see 'adapter loops': networks of adapters where the output of an adapter further down the data flow feeds back into the input of an adapter earlier in the data flow. These loops will often rely on the 'don't accept twice' mechanism to avoid getting caught into endless loops. | ||
Revision as of 22:40, 29 December 2013
An important mechanism in Crawler is the idea of 'granule acceptance' by adapters.
When a granule is presented to any adapter for processing, the adapter can accept or reject the granule based on a number of criteria.
Some of these criteria are part of the default infrastructure of Crawler, and are checked automatically. However, these automatic criteria can always be overruled by a particular type of adapter or adapter network.
The default criteria are only there for convenience: they will be 'the right thing' in most cases. They can be adjusted for the more uncommon cases where the acceptance criteria need to be different.
The first default criterium: granules are not normally accepted twice by the same adapter.
In some of the more complex personalities, you might see 'adapter loops': networks of adapters where the output of an adapter further down the data flow feeds back into the input of an adapter earlier in the data flow. These loops will often rely on the 'don't accept twice' mechanism to avoid getting caught into endless loops.
