Breaking down the process of checkout into subprocesses just seems like good sense from a software engineering point of view. The real question is should individual plugins deal with one subprocess at a time or should they deal with all of them in one module?
The answer is that it really depends on the coupling of the subprocesses. If one subprocess depends on the result of another, then it makes sense to deal with both in the same module. But if the subprocesses are independent of each other, it is much simpler to write plugins that perform a single task well. For instance, I would guess that method of order delivery doesn't depend on the payment authorization method; all 9 possible combinations could happen. In this case programming 6 individual modules is much better than creating 9 combo modules.
Update: fixed a typo.
-Mark
In reply to Re: Phases Of The Spoon
by kvale
in thread Phases Of The Spoon
by jk2addict
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |