Closing the gap between different object models

Programming language, database and operating system objects are essentially implementation variants of the same basic programming paradigm, i.e. objects as found in object-oriented programming languages. Yet, these object models differ significantly with regard to programming support, granularity, lifetime, persistence, concurrency, fault-tolerance and others. The paper points out the differences between these object models and argues that it makes sense to provide one generalized dynamic object model. A technique to define and use operating system objects in the same way as programming language objects independent from the object model provided by the underlying operating system is shown.<
>