> Just one small suggestion - if it makes just a little sense for something to
> be an interface instead of an abstract class, in the long run it is almost
> always better to make it an interface. If, under some conditions and/or JDK
> versions, interfaces are noticeably slower, I'd consider it a design bug in
> JDK and/or its JIT and assume they'd fix it in near future anyway.
> Greetings, deacon Marcus
I think the main reason for using abstract classes is not speed - but ease
of use. Servlet is an abstract class, JAXP uses abstract classes, and so
on. Most APIs that are using interfaces tend to become 'heavy' and hard to
use ( see DOM as an example - I don't want to start a war:-).
Most people will just extend the base classes ( like in SAX ) anyway.
( j.u.l is also using abstract classes ).
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
