> the application object itself serves both as a general/main handler in a chan > > of resposibility pattern we implemented and as an publisher for
> publisher/subscriber pattern thus the application object doesn't do too much
> on it own but rather serves as an information desk coordinating all the other > objects to work together

I like this approach too Arnon, I can see the chain of responsibility easily. But publisher/subscriber is a new pattern to me, any chance you have a reference on where I can read more about it? TIA!