Hi, On Monday 07 June 2004 16:20, Horst Herb wrote: > We really should each focus on designing a small module with a well defined > scope, implement it well, and publish a platform/language independent RPC > API for it. If we could work out a common *framework* in which such > independent modules can exist and cooperate efficiently (and pain free for > the developers), we would well deserve our place in the history of health > informatics. > > Horst
The idea of modules created by more or less independent groups but still can work together as building blocks and fully interchangeable is great. We should really work in this direction. But I see a problem with each group ( or module developer) freely creating his own set of RPC API's. When a software needs more than 1 module the programmer will have the burden of learning and adapting the software to use two different sets of API. Now lets say the software needs 5 modules, or perhaps 13. Well, you can imagine what happens with the programmer(s). I hope that what you mean with "common framework" is a "common set of API" that all those modules strictly adhere to. Of course, a module can implement its own special API calls for its optimization but it must also strictly implement the "common set of API". Now, another software will just use these common calls for its common needs. Once it needs a special function, thats the time the programmer must peek into the extra documentation of the module. Technically this is very easy to achieve but we all know that the problem lies somewhere else (it is not the technology). Regards, Elpidio ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
