FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2462859939> ?p ?o ?g. }

• W2462859939 endingPage "165" @default.
• W2462859939 startingPage "150" @default.
• W2462859939 abstract "Distributed objects, as applied to the term distributed object oriented systems, can be defined as those objects that have many locations on a system (network), but stemming from the way they interact with one another, appear to be coming from just one location (Taylor, 1996, p. 263). Obviously, this presents distributed-object oriented systems with design complexities because the hardware and software are not located in one place but, to the user, must look as though they are. These complexities can be well appreciated by looking at the literature. Montlick (1999) uses the very term complex in a chapter heading related to distributed object oriented systems. He attributes this building complexity to the fact that object oriented technology is in its infancy. Given that distributed object oriented systems are complex and in their infancy, it is hard to decipher a clear definition of distributed object oriented systems and the client/server (frontline computer/back-line computer) model or environment. Some such as Berson (1996) say that client/server computing is a form of distributed computing, while others such as Taylor (1996) say that client/server computing is different from distributed computing. Understanding the client/server environment adds to the complexity of understanding distributed object oriented systems. The purpose of this chapter, then, is to provide an understanding of what distributed object oriented systems are, no matter how complex they may appear to be. To provide a foundation for this understanding, the “building block” evolutionary process leading to the development of distributed object oriented systems will be given first. To foster an understanding of the systems themselves, it will be shown that no matter how complex, for a system to be distributed object oriented, basically several key ingredients must be in place. Accordingly, it will be shown that, fundamentally, distributed object oriented systems must have two object oriented properties or characteristics: encapsulation (the ability to hide code from the user) and messages (the way objects communicate). Additionally, it will be shown that software components (objects) of the distributed object oriented systems must have certain inherent features. Aside from the two object oriented properties and the certain inherent features, any critical system must have the ability to keep its data in a consistent state. This is particularly important when concurrent (at the same time) transactions (a unit of work) are executed. It was determined that because distributed object oriented systems are complex and in their infancy, in order to produce a basic definition and understanding of what they are, it would be necessary to analyze a cross-section of the current literature: i.e., information found in books, articles, journals, and Internet sources as well as information obtained from interviews with an IT expert." @default.
• W2462859939 created "2016-07-22" @default.
• W2462859939 creator A5078990742 @default.
• W2462859939 date "2011-05-24" @default.
• W2462859939 modified "2023-09-26" @default.
• W2462859939 title "Understanding Distributed Object Oriented Systems" @default.
• W2462859939 doi "https://doi.org/10.4018/978-1-878289-67-4.ch009" @default.
• W2462859939 hasPublicationYear "2011" @default.
• W2462859939 type Work @default.
• W2462859939 sameAs 2462859939 @default.
• W2462859939 citedByCount "0" @default.
• W2462859939 crossrefType "book-chapter" @default.
• W2462859939 hasAuthorship W2462859939A5078990742 @default.
• W2462859939 hasConcept C120314980 @default.
• W2462859939 hasConcept C41008148 @default.
• W2462859939 hasConcept C49312422 @default.
• W2462859939 hasConcept C81192388 @default.
• W2462859939 hasConceptScore W2462859939C120314980 @default.
• W2462859939 hasConceptScore W2462859939C41008148 @default.
• W2462859939 hasConceptScore W2462859939C49312422 @default.
• W2462859939 hasConceptScore W2462859939C81192388 @default.
• W2462859939 hasLocation W24628599391 @default.
• W2462859939 hasOpenAccess W2462859939 @default.
• W2462859939 hasPrimaryLocation W24628599391 @default.
• W2462859939 hasRelatedWork W140607976 @default.
• W2462859939 hasRelatedWork W143435555 @default.
• W2462859939 hasRelatedWork W1515904635 @default.
• W2462859939 hasRelatedWork W1571129532 @default.
• W2462859939 hasRelatedWork W157268565 @default.
• W2462859939 hasRelatedWork W2029187085 @default.
• W2462859939 hasRelatedWork W205739316 @default.
• W2462859939 hasRelatedWork W2113878270 @default.
• W2462859939 hasRelatedWork W2128027192 @default.
• W2462859939 hasRelatedWork W2285795068 @default.
• W2462859939 hasRelatedWork W2346513927 @default.
• W2462859939 hasRelatedWork W2487971875 @default.
• W2462859939 hasRelatedWork W2502391774 @default.
• W2462859939 hasRelatedWork W2798279693 @default.
• W2462859939 hasRelatedWork W9192610 @default.
• W2462859939 hasRelatedWork W2305237220 @default.
• W2462859939 hasRelatedWork W2500145525 @default.
• W2462859939 hasRelatedWork W2804982235 @default.
• W2462859939 hasRelatedWork W2890746047 @default.
• W2462859939 hasRelatedWork W2922734808 @default.
• W2462859939 isParatext "false" @default.
• W2462859939 isRetracted "false" @default.
• W2462859939 magId "2462859939" @default.
• W2462859939 workType "book-chapter" @default.