> -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED]] > > So what if you can use the command pattern without events? We > are talking > about a specific implementation that is tied to directly to > events and the > event package ;) I definetly think it should be a subpackage.
Cool, I can make it happen. > BTW Berin this is why I dislike generic names like command, > event and system > because it causes confuision not clarity ;) Codenames or > other abstract names > allow much easier understanding after initial learning curve. > They also make > it MUCH easier to have different implementations of same > style of component > or even different versions. I confess, my imagination is not good for coming up with abstract names. If you could help me out, I would appreciate it :) The benefit of *event* is that it conveys exactly what it is about: avent processing. However, your comments about .system and .component are well taken, and those names (at least .system) are placeholders until we come up with a name we like. Can someone help me with a name for .system? galahad (sp?) Sir Galahad, the green knight lancelot roundtable -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
