模板方法模式是共享Soap方法的最佳解决方案吗？

Question

I have a number of Soap Server classes most of which will need to implement 3 methods:

ping() // something to bounce a signal off to prove it has been reached
getCredentials($creds) // credentials to check sets session value
getCaller() // for logging, uses session value

As they form part of the WSDL defn they need to be public.

I am fairly sure this (I have christened it a Soaplogin) would need to be an abstract class (because it must never be instantiated on its own)

The concrete classes which extend then this core then have their own methods, none of which are shared.

I am searching for the best type of Pattern to use and am getting a bit confused, though I think a Template Method just about fits the bill - but I could just plain extend the SoapLogin class.

What advice can you give me on the best pattern to use, and maybe a preferred name for this class.

(while this uses ZF1 components it does not use full blown MVC - in case that was of importance)

Answer 1

Prefer composition over inheritance.

What you really do is you create completely independent interfaces that only by chance happen to have the same methods.

Fine. Generic methods that always do the same - that should be in a class of it's own. But not ONE class for all these methods! One class per method!

You can then add all these method classes to your server classes, and also add all the special functions the same way.

That way you can combine any of the generic functions in any way, and add another only to one API if needed.