The Postselector currently does two distinct things:
filters discovered URLs by the active Scope, then
schedules the selected URLs into the Frontier.
The first step, especially, seems appropriate for
further extension: such as remembering all rejected
URLs. We don't want people to have to subclass/extend
the crucial Postselector to do this, so we could
decompose its operation into 2 processors.
This would also give operators a chance to insert their
own extra steps between Scope-filtering and rescheduling.
Michael Stack
multimachine
1.6.0
Public
|
Date: 2007-03-14 01:38
|
|
Date: 2005-06-07 23:19 Logged In: YES |
|
Date: 2005-06-06 19:46 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| artifact_group_id | None | 2005-09-23 21:08 | gojomo |
| status_id | Open | 2005-06-07 23:19 | stack-sf |
| close_date | - | 2005-06-07 23:19 | stack-sf |
| category_id | None | 2005-06-06 19:46 | stack-sf |
| priority | 5 | 2005-06-06 19:46 | stack-sf |
| assigned_to | nobody | 2005-06-06 19:46 | stack-sf |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use