Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

ARCast.TV - Juval Lowy on Interface Based Design

Download

Right click “Save as…”

  • High Quality WMV (PC)
  • MP3 (Audio only)
  • MP4 (iPhone, Android)
  • Mid Quality WMV (Lo-band, Mobile)
  • WMV (WMV Video)
Should you use abstract classes or interfaces? What about WCF service contracts? Is the decision which one to use a design decision or a direct product of the technology at hand? Why is .NET allowing you such wide range of options, and why are other technologies (from COM to WCF) restricting you? In this ARCast, Juval Lowy of iDesign will demystify these age-old questions and share his insight and perspective with Denny Boynton.

Tags:

Follow the Discussion

  • umer_aumer_a Mario be on XBOX one day.

    Very subject to critcism and not commonly used or recomended, C++ had the rich feature of supporting multiple inheritence so there is no need to go a step back or a step aside and yet introduce interfaces [and probably rename the language C+-].

    Any one who has ever succeeded in developing a concrete application using multiple inheritence can name a lot of drawbacks in using interfaces to acheive same functionality. Like in the case of c#, the need to define interface members (i.e. overriding functions) in every class that implements the interface.  For 100 such classes implementing an interface, 100 seperate implementations for each method, required. At least multiple inheritence can reduce the number of override(d/n) functions to ensure some code reuse. If somehow interfaces are not limited to abstract definitions,......

  • People criticize C++ for multiple inheritence, which doesn't mean it is bad.  However, in many cases it is either poorly understood or otherwise misued.  MI almost always obfuscates the design and introduces maintenance issues.  This is one of the reasons why it is usually better to aggregate functionality through composition than to inherit it.  However, this is beside the point.

    Interface design is not direclty related to inheritence.  Interface design is about contract definition and abstraction from the client objects (decoupling).   This leads to easier replacement and reuse.

    Inheritence is about reuse within the server objects.  Both can lead to polymorphism, but interfaces do not have the rest of the inheritance baggage to carry along (which multiple inheritence was implemented to avoid).  But since MI leads to complexity, it didn't work out too well.

    I think Interface based design is just now being recognized as a very strong reuse mechanism, and this presentation helps to make that point.

  • I agree to Dinkhome.

    Inheritance and Interface Design are two complete different strategies and they should be used with two complete different intentions.
    When you inherit from a class you always got a hard coupling between to types.

    Interfaces are just meant to give oyu a possibility to detach types. This reduces the complexity of your software and also increases the Testability of the whole application.

    Using Interfaces as an replacement of MultiInheritance is a fault and should be avoided.

    The Use of Interface is not just about reusing components. Its about creating autarchic Modules / Components which can work and be tested , be developed stand a alone without knowing any thing more than the contract they have.

    So you can give a whole new person the task to develop a component for your 10 year old Software without to work him into the complete application.
    Just give him the Contract and let him work Smiley
  • Fans JerseysFans Jerseys

    Antti Niemi Jersey Alex Ovechkin Jersey Alexander Semin Jersey Ales Hemsky Jersey Alexandre Burrows Jersey Alexei Kovalev Jersey Andre Fleury Jersey Andrei Markov Jersey Andrew Ladd Jersey Bobby Clarke Jersey Bobby Hull Jersey Brian Gionta Jersey Brooks Orpik Jersey Chris Pronger Jersey Claude Giroux Jersey Daniel Sedin Jersey Derek Boogaard Jersey Dion Phaneuf Jersey Drew Doughty Jersey Ductin Byfuglien Jersey Duncan Keith Jersey Evgeni Malkin Jersey Gordie Howe Jersey Eric Staal Jersey Henrik Lundqvist Jersey Henrik Sedin Jersey Henrik Zetterberg Jersey Jamie Langenbrunner Jersey Jarome Iginla Jersey Jaroslav Halak Jersey Jason Spezza Jersey Jeff Carter Jersey Joe Sakic Jersey Joe Thornton Jersey John Tavares Jersey Jonathan Cheechoo Jersey Jonathan Toews Jersey Kris Letang Jersey Kris Versteeg Jersey Marc Savard Jersey Mario Lemieux Jersey Martin Brodeur Jersey Martin Havlat Jersey Maxime Talbot Jersey Michael Cammalleri Jersey Mike Green Jersey Mike Modano Jersey Mike Richards Jersey Milan Lucic Jersey Nicklas Backstrom Jersey Nicklas Lidstrom Jersey Nikals Hjalmarsson Jersey Niklas Backstrom Jersey Patrice Bergeron Jersey Patrick Kane Jersey Patrick Marleau Jersey Patrick Sharp Jersey Pavel Datsyuk Jersey PK Subban Jersey Rick Depietro Jersey Rick Nash Jersey Roberto Luongo Jersey Ryan Getzlaf Jersey Ryan Kesler Jersey Ryan Miller Jersey Scott Gomez Jersey Shane Doan Jersey Shea Weber Jersey Sidney Crosby Jersey Simon Gagne Jersey Steve Yzerman Jersey Steven Stamkos Jersey Thomas Vanek Jersey Tj Oshie Jersey Vincent Lecavalier Jersey Wayne Gretzky Jersey Zach Parise Jersey

Remove this comment

Remove this thread

close

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.