On Fri, 12 Jul 2002, Bill Barker wrote: > I know you hate interfaces :-), but this really does look like it should be > an interface at the moment.
What about abstract class :-) ? The major reason I don't like interfaces is backward compatibility issues ( like the ones we see in JDK1.4 Connection ). It'll also have some convenience methods in it - and it's easier to implement them in the base and reduce the number of methods in the provider. Plus the static method for discovery. I don't think we'll have a lot of multiple-inheritance with this. Of course, if everyone believe it's better to be an interface, I can live with that. But at least let's wait until we have an implementation and see how it works out, then we can make it interface. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
