Article Preview
Buy Now
| Print: | |
| PDF: |
Feature
Loosely coupled systems
Issue: 6.3 (March/April 2008)
Author: Norman Palardy
Article Description: No description available.
Article Length (in bytes): 21,252
Starting Page Number: 15
RBD Number: 6310
Resource File(s):
6310.zip Updated: Saturday, March 15, 2008 at 12:35 PM
Related Web Link(s):
http://en.wikipedia.org/wiki/Coupling_(computer_science)
http://activemq.apache.org/
http://stomp.codehaus.org/
Known Limitations: None
Excerpt of article text...
Wikipedia says coupling [http://en.wikipedia.org/wiki/Coupling_(computer_science) ] is "a relationship in which one module interacts with another module through a stable interface and does not need to be concerned with the other module's internal implementation."
Low coupling is a good thing. The less you rely on undocumented internal behavior of a method, class, or even an entire piece of software, the less coupled your methods and programs are. You should strive to only rely on the output or return values of a method and not on how the method achieves its results. This makes it easier to alter the behavior of a method or class when you find you need to make some change. In an RB program you, as the author, can control this quite readily.
When you have a piece of software that you write that needs to interact with other pieces of software, how do you achieve this same loose coupling? You may want to be able to permit authors to write software in REALbasic and perhaps other languages as well. Somehow you have to make it possible to be able to write "services" in as wide a variety of languages as you can. You may want some pieces written in C, some in C#, some in Java, some in REALbasic, and even others as Unix shell scripts.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.
|
