For the application programmer using DACNOS this abstraction is given at the RSC interface.
In HCS, heterogeneity is "accommodated" into certain services, but it is "abstracted" in DACNOS at the operating system level.
A project that shares the emphasis on heterogeneity and the need for a comprehensive solution with DACNOS is Cronus .
Their differences are not discussed here, because the major focus of this article is on the kernel of DACNOS.
DACNOS is considered one of the prototypes for a support environment for ODP, which is being developed by the European Computer Manufacturers Association (ECMA) .
DACNOS has tackled the subset of the SAA objectives, which are related to distributed processing in a slightly different, historically grown, mixed vendor computing environment.
The motivation for DACNOS stemmed from the demand for resource sharing in historically grown heterogeneous computer networks and the fundamental lack of appropriate support for such applications.
Feedback from applications on DACNOS has provided us with valuable insights into our design decisions.
Finally, on a platformlike DACNOS application programs are potentially portable whether or not their scope is only local or remote.
The DACNOS prototype, however, demonstrates that a functionally complete, more complex kernel can still perform very well.
The DACNOS development has taught us that in order to manage the complexity of a design effort it was extremely helpful to have a clear initial design guideline, i.
The implementation work of the DACNOS kernel was structured vertically, i.