|
-
November 14th, 2008, 04:17 PM
#1
what is meant by Loose coupling ?
what is meant by Loose coupling and its problem?
-
November 14th, 2008, 05:41 PM
#2
Re: what is meant by Loose coupling ?
Here is a good article from the MSDN:
http://msdn.microsoft.com/en-us/magazine/cc337885.aspx
It may help shed some light on loose coupling.
ahoodin
To keep the plot moving, that's why.

-
November 14th, 2008, 07:03 PM
#3
Re: what is meant by Loose coupling ?
-
November 14th, 2008, 07:07 PM
#4
Re: what is meant by Loose coupling ?
 Originally Posted by honeyboy_20
what is meant by Loose coupling and its problem?
Loose coupling is the SOLUTION to a series of problems, the looser the better.
Tight coupling, basically means something made up of ttwo or more parts, where the parts can NOT be used individually.
Code:
class Driver
{
public Car ar;
}
class Car
{
}
Driver is tightly to Car, and can not be used without it.
TheCPUWizard is a registered trademark, all rights reserved. (If this post was helpful, please RATE it!)
2008, 2009,2010
In theory, there is no difference between theory and practice; in practice there is.
* Join the fight, refuse to respond to posts that contain code outside of [code] ... [/code] tags. See here for instructions 
* How NOT to post a question here
* Of course you read this carefully before you posted
* Need homework help? Read this first
-
November 19th, 2008, 05:44 AM
#5
Re: what is meant by Loose coupling ?
I would say that what you are talking about is a difference between association and aggregation. As I understood loose coupling vs. tight coupling, it is about a knowleadge of specific type of associated object, so the client rely on the specifict type (tight) rather that on its contract (loose).
- Make it run.
- Make it right.
- Make it fast.
Don't hesitate to rate my post. 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|