Jaehong, Although what you say is mostly true, definition of an interface is ideally the minimum set of functionality of the consumers of the interface. When a library exposes too much in an API, you run into the same issues that you are expressing including high dependence between layers, a reduction in reusability, higher maintenance, etc. So, if an API that is NOT used by the intended consumers becomes required, you have, in fact, created additional dependencies that results in most of the problems that you are stating. Pat
From: ??? [mailto:[email protected]] Sent: Thursday, July 23, 2015 8:44 AM To: Lankswert, Patrick; Kesavan, Vijay S; Light, John J; iotivity-dev at lists.iotivity.org Subject: RE: [dev] CAGetNetworkInformation() function does not work Pat, Vijay I say independence is not a structural separation. John said the CA APIs will disappear in the near future. CA layer abstracts the platforms and connectivity types to provide unified transport interface and RI layer manages resources regardless platforms and connectivity types. If two layers are used without interface, occurs tight coupling.
