Design questions for future filter model.

>BTW: While you seem to think a lot these days ;-) if you have any
>other serious design flaws to mention, it is really the right time to
>speak up.
>
>Anselm.

Ok, one more thing on my mind.

With new filter model, are there any considerations to allow filters to
specify in which order they want to be. For example, we might want Auth
filter to be called before all the others and not just because it starts
with 'A'. But at some later point somebody might right a filter that should
sit before Auth filter and its derivatives, but anywhere if Auth filter is
not there. Other examples could be a global and localised filter that work
in pairs. They might want to be executed in some particular order relative
to each other but in any order relative to other filters. Also, it might be
required for some of the filters you mentioned before (Lookup filter in
particular).

The integrity of constrains could be checked by using modified bubble sort
at "Add filter" time. If filters are conflicting in their requested order,
then a filter cannot be added.

It would be great if filters could register their requirements on filters
they are executed before and after.
Using any other not so flexible system (eg. Alphabetical) would bring
problems. (as people with Machintoshes know too well :-{ )

Regards,
 Alex.

Ps. If you are aware of this problem (idea) and already have some
alternative solution, I would welcome the explanation.

Pps. If you liked the idea, I could probably help with writing some code for it.

alex@access.com.au

Received on Tuesday, 13 August 1996 21:07:16 UTC