On Sun, Oct 26, 2008 at 11:07 AM, Nader Aeinehchi <[EMAIL PROTECTED]> wrote:
> What is thread safety policy of Qi4j? Policy is not explicit, but in principle; Only internals to the Qi4j Runtime which can not be otherwise protected are to be thread-safe. In practice, it is a similar position as the difference between the Hashtable and HashMap. Hashtable thread-safety is on paper a good idea, but the fact that it is seldom enough to protect a single object, its performance impact greatly reduced its usefulness vs the HashMap. That said, if the DDD principle of aggregates not exposing internal state, it should be rudimentary to create a thread-safety Concern, that is applied to aggregates, and simple solution to the problem. Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
