Hi All,
Hope everyone had a great weekend.
I've just been looking at the Fortress Component/Service
Manager/Selector classes, and seen that there's a bit of
duplicated code there.
I was thinking of changing the implementation so that a
FortressComponentManager actually uses a FortressServiceManager
internally, and likewise with FortressComponentSelector. That would
reduce a lot of code and make things easier to manage/change.
The only difference between the 2 seem to be the final cast to
Component upon lookup, and the hasService/hasComponent method names.
I just wanted to check first if this was a fair assumption to make ?
ie. that a ComponentManager can be implemented in terms of a
ServiceManager (ditto for ComponentSelector). Does anyone see any
problems there ?
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
