hey all,

i'm reading about app architecture in patterns and practices and there was a
paragraph i need some clarification on. please keep in mind that i'm new to
this object oriented stuff so talk lamen.

Here's the paragraph:
Understand how components communicate with each other before choosing
physical distribution boundaries. Keep coupling low and cohesion high by
choosing coarse-grained, rather than chatty, interfaces for remote
communication.
End of paragraph.

What does coarse-grained mean in this sense? or chatty?

thanks,
rodchar

Don't try to create one interface that does everything. Group
functionalities into several smaller and more managable interfaces. This
enables you to implement one interface in one class and another interface in
another class rather than having to create huge monolithic classes that
*have* to implement the whole interface.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.





"rodchar" <(E-Mail Removed)> wrote in message
news:760CAD21-8B9D-4C76-A70C-(E-Mail Removed)...
> hey all,
>
> i'm reading about app architecture in patterns and practices and there was
a
> paragraph i need some clarification on. please keep in mind that i'm new
to
> this object oriented stuff so talk lamen.
>
> Here's the paragraph:
> Understand how components communicate with each other before choosing
> physical distribution boundaries. Keep coupling low and cohesion high by
> choosing coarse-grained, rather than chatty, interfaces for remote
> communication.
> End of paragraph.
>
> What does coarse-grained mean in this sense? or chatty?
>
> thanks,
> rodchar
>

Hi rodchar

I would say that this is to do with the creating a distributed application
architecture - network round trips are expensive and slow.

So make sure that your design takes this into account. Rather than having a
class with multiple independent properties, which in a distributed
application could involve mutiple round trips across the network, design your
classes to do as much work as possible in a single round trip.

HTH

Nigel Armstrong

"rodchar" wrote:

> hey all,
>
> i'm reading about app architecture in patterns and practices and there was a
> paragraph i need some clarification on. please keep in mind that i'm new to
> this object oriented stuff so talk lamen.
>
> Here's the paragraph:
> Understand how components communicate with each other before choosing
> physical distribution boundaries. Keep coupling low and cohesion high by
> choosing coarse-grained, rather than chatty, interfaces for remote
> communication.
> End of paragraph.
>
> What does coarse-grained mean in this sense? or chatty?
>
> thanks,
> rodchar
>

Thank you for the great replies.

"rodchar" wrote:

> hey all,
>
> i'm reading about app architecture in patterns and practices and there was a
> paragraph i need some clarification on. please keep in mind that i'm new to
> this object oriented stuff so talk lamen.
>
> Here's the paragraph:
> Understand how components communicate with each other before choosing
> physical distribution boundaries. Keep coupling low and cohesion high by
> choosing coarse-grained, rather than chatty, interfaces for remote
> communication.
> End of paragraph.
>
> What does coarse-grained mean in this sense? or chatty?
>
> thanks,
> rodchar
>