skizz.biz

We started a scary spike last night — putting a transparent ‘Type 3’ Event Driven architecture in Pico.

The idea is simple — suppose I have a Kissable interface:

public interface Kissable {
public void kiss();
}

I add some Kissable things to my Type3MsgPicoContainer:

container.registerMulticasted(Kissable.class, new Girl());
container.registerMulticasted(Kissable.class, new Grandmother());
container.registerMulticasted(Kissable.class, new Baby());
container.registerMulticasted(Kissable.class, new BlarneyStone());
container.registerMulticasted(Kissable.class, new Boy());

I also add something that understands how to kiss:

public class Boy{
public Boy(Kissable kissable) {...}
public void doSomeKissing()
{
kissable.kiss();
}
}
Boy boy = new Boy()
container.register(Boy.class, boy);

If I now do boy.doSomeKissing(), an event is generated and queued internally and (asynchronously) all Kissables in the system get kissed.

Joe Walnes suggested we call this ‘Type 3 Messaging’ since it hides the implementation in the same way that Pico itself does — and looks like ‘plain old message calls’.

In tha spike we did last night (you can see the source code here ) we use concrete objects and support round-robin multicasting as well.

Other strategies migt be available too — for example a pooled implementation for database components, or a transparent SEDA style architecture.

This entry was posted on Thursday, September 11th, 2003 at 1:48 pm and is filed under life. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.