On Tue, Jun 10, 2008 at 4:34 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote:
> At lookup time the chain is > assigned a particular composite instance and mixin, and the call is then > proceeded. Very interesting "challenge".... ServiceComposite --> Agree a no-brainer. Static assignment. EntityComposite --> I think the answer might not be as simple as you portrayed. Even if Entities are short-lived, in web applications you might have hundreds or even thousands of requests in progress at the same instance of time, in which case the number of objects becomes large, and the explosion of objects actually happens. For other types of applications, it might be true that extremely low numbers of Entities (ValueComposites probably have a similar argumentation) are present, but where speed is paramount. So, I think the solution is to provide the "Turbo" button for users to turn on or off for each app, or even each type. How that "button" is implemented is a different story. IMHO, is this really a "design decision"??? Isn't this largely an internal implementation detail, which we can introduce later? Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
