+1 credit
| Version | Summary | Created by | Modification | Content Size | Created at | Operation |
|---|---|---|---|---|---|---|
| 1 | Sirius Huang | -- | 2180 | 2022-09-30 01:39:48 |
Video Upload Options
In computing, the System Object Model (SOM) is an object-oriented shared library system developed by IBM. DSOM, a distributed version based on CORBA, allowed objects on different computers to communicate. SOM defines an interface between programs, or between libraries and programs, so that an object's interface is separated from its implementation. SOM allows classes of objects to be defined in one programming language and used in another, and it allows libraries of such classes to be updated without requiring client code to be recompiled. A SOM library consists of a set of classes, methods, static functions, and data members. Programs that use a SOM library can create objects of the types defined in the library, use the methods defined for an object type, and derive subclasses from SOM classes, even if the language of the program accessing the SOM library does not support class typing. A SOM library and the programs that use objects and methods of that library need not be written in the same programming language. SOM also minimizes the impact of revisions to libraries. If a SOM library is changed to add new classes or methods, or to change the internal implementation of classes or methods, one can still run a program that uses that library without recompiling. This is not the case for all other C++ libraries, which in some cases require recompiling all programs that use them whenever the libraries are changed, known as the fragile binary interface problem. SOM provides an application programming interface (API) that gives programs access to information about a SOM class or SOM object. Any SOM class inherits a set of virtual methods that can be used, for example, to find the class name of an object, or to determine whether a given method is available for an object.
References
- SOM and Object REXX by Dr. Willis Boughton (August 2004) http://www.edm2.com/index.php/SOM_and_Object_REXX
- SOMobjects for OS/390 documentation http://www-03.ibm.com/systems/z/os/zos/library/bkserv/os390_r10pdf/#som
- Tandem Leverages IBM's SOMobjects Technology for Distributed Object Computing http://www.thefreelibrary.com/Tandem+Delivers+Enterprise+Transaction+Processing+Capabilities+to...-a018607143
- Ira R. Forman and Scott Danforth (1999). Putting Metaclasses to Work. ISBN 0-201-43305-2. Chapter 11 "Release-to-Release Binary Compatibility", page 246An article with identical name and similar contents of the same author can be found on the Web: Release-to-Release Binary Compatibility http://hobbes.nmsu.edu/h-viewer.php?dir=/pub/os2/doc&file=R2R_SOM.zip
- "List of ArcaOS 5.0 WPS Classes". http://www.edm2.com/index.php/List_of_ArcaOS_5.0_WPS_Classes.
- Lost in the Garden by Roger Sessions (August 1996) http://www.edm2.com/index.php/Lost_in_the_Garden
- Just a little SOM thing for Linux developers by Esther Schindler (February 2008) http://blogs.cio.com/esther_schindler/a_little_som_thing
- Reviving OS/2's best in the Linux desktop by Steven J. Vaughan-Nichols (February 2008) http://www.desktoplinux.com/news/NS7822082064.html
- The OS/2 petition, second round (2007–2010) https://web.archive.org/web/20070227095059/http://www.os2world.com/petition/
- Binary Compatibility Issues With C++ https://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++
- ComponentGlue(tm) Provides Full Interoperability with OLE, OCX Controls http://www.novell.com/news/press/archive/1995/02/pr00063.html
