Linked by Thom Holwerda on Sun 4th Sep 2005 10:15 UTC, submitted by Lumbergh
KDE "RuDI is an architectural approach whose goal is to achieve loose coupling among interacting software components instead of linking to libraries. A service is a unit of work of the desktop done by a service provider to achieve desired end results for a 3rd party service consumer. How does RuDI achieve loose coupling among interacting software agents? It does so by employing two architectural constraints: An extensible XML schema allows new versions of services to be introduced without breaking existing services. Second we send messages over a protocol instead of calling explicit individual member functions."
Permalink for comment 27198
To read all comments associated with this story, please click here.
Bad Idea
by Luke McCarthy on Sun 4th Sep 2005 11:33 UTC
Luke McCarthy
Member since:

You're going to need to call some function or other, which means you need to define some API even if that is carried across a protocol. KDE is slow enough as it is. You could achieve the same damn thing by linking to different stub libraries that call the changing real API. Either way this isn't free: you need to keep the "XML schema"/protocol or stub library or whatever up to date, and you incur run-time overhead for what I would argue very little gain.

Reply Score: 1