In this article, Lamont Adams explains the basic idea behind the term, which flies in the face of traditional object-oriented design doctrine, and clue you in to why chunkiness may be the way to go.
A “chunky” interface may be a new concept to some, but chunkiness is an idea you need to be familiar with if you plan to develop distributed .NET applications anytime soon.
What is chunky?
In basic terms, a chunky interface is one that accomplishes a maximum amount of work with a minimum number of object method calls. By way of example, let’s look first at how you’d traditionally create a COM object in VB6:
Dim o as new SomeObject
o.SomeProperty = “Some value”
o.SomeOtherProperty = “Some other value”
|