You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@struts.apache.org by DG...@EvergreenInvestments.com on 2005/08/10 16:54:56 UTC

[OT ]Re: Why interface

"Program to an interface, not an implementation." 

#1 principle from GoF.  Here's a recent interview with Erich Gamma: 
http://www.artima.com/lejava/articles/designprinciples.html

-Dennis




Carl Smith <cc...@yahoo.com> 
08/10/2005 10:47 AM
Please respond to
"Struts Users Mailing List" <us...@struts.apache.org>


To
Struts Users Mailing List <us...@struts.apache.org>
cc

Subject
Why interface







In Java/J2EE community, it seems that a lot of experienced developers tend 
to use a lot of interfaces, however, a lot of junior developers ignore 
using interface. I am not sure why interfaces seem to be favorite to some 
experienced developers. Can some one explain this?Can you give examples 
where an interface is preferred?

Thanks.

 



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com