> In both case, I think that the primary concern for us would be the > "Availability Contract", which somehow communicate with the component when > other components are available or not. Because once that is defined in > framework, both the above patterns, and re-loadable traditional AF4 > components, can be implemented in the container.
Looking at some of the work done by Berin and Vince on the GUIAPP stuff it looks as though they have made Excalibur the hub by making event subscription a life-cycle method. This is an interesting slant to the use of the pattern that should be explored somewhat. BTW here are some likes to d-haven which contains guiapp and to the exact pattern used by both d-haven and Eve's frontend: http://sourceforge.net/projects/d-haven pattern (thanks to Vince) : http://members.ispwest.com/jeffhartkopf/notifier/ Eve documentation explaining it's use in the frontend: http://incubator.apache.org/directory/subprojects/eve/frontend/events.html We certainly should explore this pattern and its effects on IoC and its potential use as a life-cycle etc. It helps me get rid of cyclic dependencies between components and even maven subprojects. Take a look at this: http://incubator.apache.org/directory/subprojects/eve/source-layout.html Look at the section on Subsystem Directories and Common APIs. Alex Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
