On Tue, Aug 12, 2008 at 2:10 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote:
> Crazy thoughts ahead. You have been warned! I disagree completely!!! These are not crazy, but very good ideas! ;o) Don't forget that many messaging systems are effectively RDBMS tables with a set of funky queries. I am sure there are many messaging systems out there, but many have exactly the problems you describe, and often being incredibly complicated to configure and connect to. I am by no means an expert either, and perhaps we should consult those, but I see a couple of things in these kinds of systems; 1. Transaction-oriented. With our UnitOfWork and a future worked out way how to make cross-UoW completes(), I think we are pretty set. 2. Message Type. This corresponds directly to our Entity type, and should be no problem. 3. Topic. Most systems allows some form of publish/subscribe mechanism over a "Topic", being orthogonal of the Message Type. Topic seems to be a feature we need to figure out. I think (but not sure) that the Topic is needed to be calculated in runtime, and not statically set at development. I can see two ways on how to implement Topics; 1. Require a "MessageEntity" type, which has a Topic property. 2. Add the Message instance to a Topic "Association tree", and the EntityStore deals with that. In general, I think you are on to something pretty neat, and the 'sending side' is probably pretty straight forward. I think we need to look at the consumer before deciding. Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
