Re: how about making upgrades easier

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: how about making upgrades easier
by Naasking on Wednesday 11/Apr/2001, @12:16

Isn't this supposed to be the benefit of components though? You write components that can operate independently(and can co-operate) so you don't have to upgrade EVERYTHING to add one feature to your suite/app/whatever. You just have to upgrade the component which is dynamically loaded when needed. If the component wasn't there to begin with, it should be just a matter of installing it and having it registered with whatever service links the components with the services they provide.

Sure reuse, protection, network transparency are all cool component features too, but the main benefit of componentization is supposed to be complete separation of implementation from interface. If this isn't currently the case, then I'd say it's time to rethink the strategy behind the current component framework.

Related Links

·   Articles on KDE Official News
·   Also by Naasking
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"Soon the whole Caldera office will be busy playing KPat, not answering any mails or phone calls anymore." -- Simon Hausmann
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.