Sylvain Wallez wrote: > > So I started refactoring ECM++ so that a selector doesn't > manage components itself but adds them to its service > manager, and also delegates select() to this manager. This > actually "flattens" the component space, thus allowing > variations of a given role (what normally goes into > selectors) to come from different sources. This is nearly > done (still some problems for selectors nested in selectors), > and <import> should come soon after. > Sounds great. ECM++ did already part of it, or more precisly it did it the other way round: you could lookup a component using the fortress syntax and this was delegated to the appropriate selector.
Carsten
