Hi, > > I began to realize a trend > > emerging after I introduced a central publish and > subscribe facility. The > > pattern decouples components by enabling > communication using events and the > > notifier pattern. This also lead to the > disappearence of methods on service > > interfaces. > Interesting , Some problems with Implicit Invocation(event,pub/suc,notifier...) is :- . loss of control (which components responded,when did the other component finish its task, order of flow of events). In some case these might not be important at all(pure loosely coupled) and in some we might build it using protocols (req-reply,ack) but it muddies the implementation. So it doesnt seem like a cure for all types of component interactions. . lots of events esp when maintaining frequently-used shared data/interaction across such components.I think maybe its less intuitive too at times esp when its a chain of events/actions.
But its a well researched area(google(implicit inovation)) & a pretty interesting one too. Regards, Vinay __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
