Rails spinoffs - Aug 2005 - [PATCH] do not use beforeStart, afterFinish, beforeUpdate, and afterUpdate internally in combination effects

Hello,

my patch separates usage of the callback between the user, combination
effects, and the core effects.

Consider these use cases.

a) user - core effects
b) user - combination effects - core effects

For a), the existing callbacks can be used by the user
For b), the existing callbacks are partly used by the combination
effects as a communication channel to the core effects, therefore they
cannot be used as a channel between the user and the combination
effect in these cases.

My patch introduces *Internal callbacks as twins to the existing ones.
The result is, that the user can always use the normal callbacks in a)
and b), necessary communication internal to the effect in b) is done
by the *Internal callbacks.


Bye,
  Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: effect_callcack_separation.diff
Type: application/octet-stream
Size: 8079 bytes
Desc: not available
Url :
http://wrath.rubyonrails.org/pipermail/rails-spinoffs/attachments/20050825/403eb026/effect_callcack_separation.obj