Prasun Dewan and Rajiv Choudhary, "Experience with the Suite Distributed Object Model," Proceedings of IEEE Workshop on Experimental Distributed Systems, October 1990, pp. 57-63.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....are relatively untested. The only reported applications of distributed objects known to us are the Eden [1] and Clouds [4] distributed operating systems, the Edmas distributed mail system [2] the CES multi user document editor [12] and the simple object based Suite applications described in [7]. Moreover, to the best of our knowledge, generation of multi user editors is unique to Suite and has so far been used to generate only simple demonstration applications such as the ones mentioned in [8] Our implementation effort has demonstrated the usefulness of these technologies. It has also ....

....use. Moreover, there was no straightforward way to combine them. Our solution uses the experimental technologies of distributed objects and multi user editor generators. Both technologies were crucial to making our implementation task tractable. While we had some experience with these technologies [7, 8], we had not used them to build an application of this complexity. In this section, we motivate our choice of these technologies and the ways in which we used them. Data Model Our first task was to choose a data model for describing the information. Traditionally, two data models have been used ....

[Article contains additional citation context not shown here]

Prasun Dewan and Rajiv Choudhary, "Experience with the Suite Distributed Object Model," Proceedings of IEEE Workshop on Experimental Distributed Systems, October 1990, pp. 57-63.

....systems including Smalltalk and Dost, these objects execute in separate address spaces, residing possibly on different hosts. Each object is associated with an ASCII name, which is used by other objects to communicate with it. This name is a file name in a hierarchical network file system [9] and is given at object creation time as an argument to the application program executed by the object. Thus, a user can execute the commands cd u13 rxc proj demo serctool budget name my budget projects name my projects budget my budget affiliates name my affiliates budget my budget to ....

....fact that the object was passivated since the last time he or she interacted with it. There is, however, an extra delay in connecting to the object, which depends on the size of its persistent data. Our experience shows that this delay is imperceptible when the size of the persistent data is small [9]. 2. Programming Primitives Each one of the objects of the example tool executes a separate application program. Figure 11 shows an outline of the application program executed by the affiliate object. It is a C program containing special comments beginning with the words oc and dmc, called object ....

[Article contains additional citation context not shown here]

Prasun Dewan and Rajiv Choudhary, "Experience with the Suite Distributed Object Model," Proceedings of IEEE Workshop on Experimental Distributed Systems, October 1990, pp. 57-63.

....always physically separated. Physical separation does increase the overhead of communicating among the components and for each application this cost must be weighed against the benefits offered by physical separation. Our experience shows that this cost is often negligible in current environments [6]. Therefore, we believe that a UIDE must give the application programmer end user the option of physical separation. The benefits of physical separation can also be obtained by replicating the complete application (including the functional component) on each user s workstation [10, 17] However, ....

Prasun Dewan and Rajiv Choudhary, Experience with the Suite Distributed Object Model, Proceedings of IEEE Workshop on Experimental Distributed Systems, pp. 57-63 (October 1990).

....on UNIX) to inform interested objects about changes to data structures maintained by them. Indeed, as mentioned above, one of the advantages of supporting objects is that polling of data encapsulated by them is unnecessary. More details on our experience with the Suite object layer can be found in [12] 5. CONCLUSIONS AND FUTURE WORK The Suite object model was developed to support loose coupling between the interactive and computational components of interactive applications, and collaborative applications. It provides persistent distributed, shared, and protected objects, and has been ....

Prasun Dewan and Rajiv Choudhary, Experience with the Suite Distributed Object Model, Proceedings of IEEE Workshop on Experimental Distributed Systems, pp. 57-63 (October 1990).

....disadvantage of indirect physical coupling is the cost of sending an extra message to the application. However, our experience with using applications among users connected via a local area network shows that this cost is not noticeable and is negligible in comparison to the screen update cost [7]. Clearly, this may not be true when users are interacting from sites connected via slower networks. Another disadvantage of this approach is that the application can become a central bottleneck. We plan to test our applications across wide area networks and with large numbers of users and support ....

Prasun Dewan and Rajiv Choudhary, "Experience with the Suite Distributed Object Model," Proceedings of IEEE Workshop on Experimental Distributed Systems, October 1990, pp. 57-63.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC