From: Miguel A. B. L. <mig...@ho...> - 2006-02-18 11:55:14
|
>well, these interfaces were planned as a logical start for another ruleset. >The interface way is the most elegant way, it does not block stuff for >further development (using (abstract) base classes do this some times). A >good example are the List, Map, Set and Iterator interfaces, same "we dont >want to enforce a base class" idea. > >If we do not plan to implement another ruleset these can be removed, but I >remember that Ragnar wanted to develop an alternative one. If it is still >an option these interfaces should not be replaced by classes. My "problem" is that the ruleset idea is a bit incompatible with the API at Server, so we need to choose one of them( API or rulesets ). I will keep with it as it is now, but we need to fix it ASAP. I won't remove it by now unless the problem start to get important. I am completing API at Client. |