Programming where components establish contracts with each other via published interfaces. Similar to ComponentBasedDevelopment
. The latter focuses on the architecture and framework aspects of the entire application, while this page focuses only on the interface and communication aspects.
. -- SachinRaverkar
An example of MicroSoft VbClassic
description is found at
[May not last long, as MicroSoft
is quickly removing references to information on preDotNet
architecture and technologies. A summary by someone with working knowledge may help those who have to maintain DistributedInternetArchitecture
Another article found on web:
Looks good but too much reading already.
mentioned that VbClassic
works as glue code.
The article from ZDnet called "Microsoft steers away from object orientation" dated Jan2004 probably reported on the same conference that DonBox
spoke. It is found at
the point that gets me thinking is:
is implemented, would ComponentBasedDevelopment
fade away, but InterfaceBasedProgramming
continues, in a different format?"
What I ask may not make sense due to my limited knowledge. But that is how the community can help me, and though its efforts, help other readers later as well.
At a programming interface level, please refer to AreComponentsObjects
EditText of this page
(last edited July 24, 2007)
or FindPage with title or text search