Ticket #131 (new enhancement)
Opened 6 months ago
operation filters now vote on an operatin rather than exclude them
| Reported by: | serialseb | Owned by: | serialseb |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Core - Pipeline | Version: | |
| Keywords: | Cc: | ||
| Time remaining: | 1d | Blocked By: | |
| Time spent: | 1d | Time planned: | 1d |
| Blocking: |
Description
The filters currently execute one after the other, unselecting methods as they go.
This is a problem for distributed extensibility in the framework.
The filters need to all be executed on all existing operations, and for each time a filter returns that operation, a vote is cast. We then pass all the methods with vote > 0, sorted by vote count, down the pipeline.
Attachments
Note: See
TracTickets for help on using
tickets.
