Being keen about API architectures ... > -----Original Message----- > From: Benedikt Ritter [mailto:brit...@apache.org] > Sent: Sunday, June 19, 2016 07:08 > To: Commons Developers List <dev@commons.apache.org> > Subject: Re: [CRYPTO] Defining the public API; are its interfaces > supposed to be implemented or just used? > > My unterstanding of crypto is that those interfaces are not to be > implemented by Clients. > > sebb <seb...@gmail.com> schrieb am So., 19. Juni 2016 um 14:02: > [ ... ] > > Users deriving from an abstract base class do not have to change code > > to implement new methods. > > But if their class happens to define a method with a name that is > > subsequently used by the Crypto abstract class, there will be a clash > > which will require them to recode. [orcmid]
It is my understanding that this difficulty is one that Interfaces can be used to overcome. It also does not compel all implementations being off the same [abstract] base class. - Dennis > > > > > Jochen > > > > > > > > > -- > > > The next time you hear: "Don't reinvent the wheel!" > > > > > > > > http://www.keystonedevelopment.co.uk/wp- > content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg > > > > > > -------------------------------------------------------------------- > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
