----- Original Message ----- From: "Mu Mike" <[EMAIL PROTECTED]>
> dont you think this is too strict? If you down_cast your interface to an implementation why do you need Avalon anyway? The interface represents a service, and your client should no be aware - or care - about its implementation. From time to time the implementation can be changed and your clients would broke if you use in the way you proposed. > every implementaion of a Service must have all its public methods declared > in the interface,and if you happen to need to add a public method to a > specific implemetation class, you must declare it in the Interface,and > since other implementations may need not use that method, you will have to > have an abstract class also,just such a right rule. Maybe you have a not well design application. Try to search for holes in the services contracts, not in Avalon. regards, hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
