On Monday 14 April 2008 22:25, Rickard Öberg wrote: > But that's no good since it forces all side-effects to be handled the > same way. If I have three side-effects on the same method I may want > them all to be handled differently, hence forcing the implementor to > deal with it will work, and the framework is less responsible for > ensuring that objects are valid when the side-effect actually executes > (VERY important).
I still disagree. IMHO, it looks like neither the SideEffect, nor the MixinType will be fully aware of the entire context, hence building in assembly concerns into the domain models. I think it will also make usage of asynch SideEffects much harder, and if this is the way we go, then I will strongly suggest we drop Async notion all together for now. I think that the example you tried to show, can be done without any new features in Core, and perhaps that is what you are trying to say. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
