P. Wycko#, S. W. McLaughry, T. J. Lehman, and D. A. Ford. T Spaces. IBM Systems Journal, 37(3):454-- 474, 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....data space presented to mobile hosts How is it made persistent The solutions developed to date basically di#er depending on the answers they give to the above questions. We now review three tuple space middleware that have been devised for mobile computing applications: Lime [45] TSpaces [77] and L2imbo [17] Lime In Lime [45] the shift from a fixed context to a dynamically changing one is accomplished by breaking up the Linda tuple space into many tuple spaces, each permanently associated to a mobile unit, and by introducing rules for transient sharing of the individual tuple ....

....relationship; finally, reactions can be set on the tuple space, to enable actions to be taken in response to a change in the configuration of the system. An important aspect of Lime is tuple access and movement; events are used to notify users when a new tuple is available. TSpaces TSpaces [77] is an IBM middleware system. The goal of TSpaces is to support communication, computation and data management on hand held devices. TSpaces is the marriage of tuplespace and database technologies, implemented in Java. The tuplespace component provides a flexible communication model; the database ....

P. Wycko#, S. W. McLaughry, T. J. Lehman, and D. A. Ford. T Spaces. IBM Systems Journal, 37(3):454--474, 1998.

....approach, of which tuple space based models are variants, is one of the most appreciated, also because of its flexibility. Evidence of the success gained by the tuple space paradigm is given by the many tuple space based run time systems, both from industries, e.g. JavaSpaces [32, 2] and TSpaces [35], and from universities, e.g. PageSpace [13] WCL [30] Lime [28] and TuCSoN [27] Many type systems for guaranteeing security properties have been proposed for process calculi with distribution and mobility, but, as far as we know, ours is the first one implementing such fine grained policies. ....

P. Wycko#, S. McLaughry, T. Lehman, and D. Ford. TSpaces. IBM Systems Journal, 37(3):454--474, 1998.

....approach, of which tuple space based models are variants, is one of the most appreciated, also because of its flexibility. Evidence of the success gained by the tuple space paradigm is given by the many tuple space based run time systems, both from industries, e.g. JavaSpaces [33, 2] and TSpaces [36], and from universities, e.g. PageSpace [13] WCL [31] Lime [29] and TuCSoN [28] Many type systems for guaranteeing security properties have been proposed for process calculi with distribution and mobility, but, as far as we know, ours is the first one implementing such fine grained policies. ....

P. Wycko#, S. McLaughry, T. Lehman, and D. Ford. TSpaces. IBM Systems Journal, 37(3):454--474, 1998.

....rests on an extension of the basic Linda coordination model [13] with multiple distributed tuple spaces. General evidence of the success gained by the tuple space paradigm is given by the many tuple space based run time systems, both from industries, e.g. SUN JavaSpaces [1] and IBM T Spaces [22], and from universities, e.g. PageSpace [8] WCL [21] Lime [19] and TuCSoN [18] Klaim programming paradigm enjoys a number of properties, such as time uncoupling, destination uncoupling, space uncoupling, modularity, scalability and flexibility, that make the language appealing for open ....

P. Wycko#, S. McLaughry, T. Lehman, and D. Ford. TSpaces. IBM Systems Journal, 37(3):454-- 474, 1998.

....approach, of which tuple space based models are variants, is one of the most appreciated, also because of its flexibility. Evidence of the success gained by the tuple space paradigm is given by the many tuple space based run time systems, both from industries, e.g. JavaSpaces [40, 3] and T Spaces [41], and from universities, e.g. PageSpace [14] WCL [37] Lime [35] and TuCSoN [34] Moreover, the Klaim programming paradigm puts forward a clear separation between the programmer level and the net coordinator administrator level. Programmers write processes, while coordinators write nets, hence ....

P. Wycko#, S. McLaughry, T. Lehman, and D. Ford. TSpaces. IBM Systems Journal, 37(3):454--474, 1998.

....communicate with each other, knowing the space su#ces. The bootstrapping activity is reduced to getting hold of a suitable space. A number of technologies are emerging to take care of this issue [Sun00b, Mic00, Sal99, Hew01] As a consequence a number of coordination frameworks have been proposed [Wyc98, Sun00a, PMR99] # Spaces is based on the abstraction provided by coordination frameworks but does not commit itself to any particular technology. Indeed we carefully designed its architecture as to be independent of the coordination framework of choice. Space Figure 1: # Spaces Architecture ....

....storage area. # Spaces is not linked to a particular space implementation, indeed any coordination framework reasonably powerful can be plugged in the framework by writing a suitable driver. The current implementations provides a choice of drivers to be used with the TSpace coordination framework [Wyc98, Leh97, Eus99, LMW99, TLE 99, LCX 01] developed at IBM research. This choice is by no means binding, it would be entirely possible for users to write their own space implementations. The requirements on the coordination framework are relatively light: Support for the write, take, scan ....

P. Wycko#. Tspaces. IBM Systems Journal, 37(3), August 1998. 62

....operation is not de ned [7] 1.4. Fault tolerant tuple spaces. Early tuple space based languages su ered from poor fault agent (program, process) fault tolerance. Later, many systems have used transactions to provide fault tolerant Linda primitives: PLinda [6] JavaSpaces [14] and TSpaces [16]. More recently Rowstron [12] proposed a new technique mobile coordination in order to provide fault tolerant tuple space based co ordination. Transactions. Most implementations which use transactions add two new primitives which are start and commit [12] The start primitive causes the server ....

P. Wycko, S. McLaughry, T. Lehman, D. Ford, TSpaces, IBM System Journal, 1998.

....One set of such primitives are those that allow reactive programming, essentially allowing a program to be noti ed on the insertion of tuples into particular tuples spaces, or dataspaces. Examples of Lindalike coordination languages including such primitives are JavaSpaces [W 98] TSpaces [WMLF98] and WCL [Row98] One interesting observation is that the primitives incorporated within the coordination languages, whilst all aiming to provide support for reactive programming, have di erent (informal) semantics. Indeed, it is possible to classify the primitives incorporated as being: 1) ....

P. Wycko, S. McLaughry, T. Lehman, and D. Ford. T spaces. IBM Systems Journal, 37(3):454-474, 1998.

....adopted in a huge variety of systems and applications, going from parallel computing to Web based collaboration system. Recently, this communication mechanism has been adopted also by several proposals of coordination platforms (see, e.g. Sun Microsystems JavaSpaces [W 98] or the IBM T Spaces [WMLF98] for the management of dynamically recon gurable federations of devices, where processes cooperate and compete for the use of shared resources. In this paper we investigate the scalability of this coordination approach to the realm of peer to peer systems. Informally, peer to peer (P2P) ....

P. Wycko, S. McLaughry, T. Lehman, and D. Ford. T spaces. IBM Systems Journal, 37(3):454-474, 1998.

....foundation to deploy a Web implementation; however, Web attempts to achieve far more than just service discovery. In particular, we are also interested in providing a transactional framework where services are the basic operations and to provide fault tolerance and persistance. T Spaces [18] provide a middleware architecture with database capabilities. This approach is complimentary to our approach in the sense that it addresses a number of orthogonal issues. In particular, TSpaces can be used to create a Webf implementation. 14 7 Conclusions The web is growing exponentially, both ....

P. Wycroft, S. W. McLaughry, T. J. Lehman, and D. A. Ford. Tspaces. IBM Systems Journal, August 1998. http://www.research.ibm.com/journal/sj/373/wyckoff. html. 16

....of per node attributes, or of tags generated from node data by arbitrary functions. View materialization gives TerraDir the ability to name objects and resources by attribute, a functionality provided in some form or another in Intentional Naming [8] the Information Bus [34] and T Spaces [47], as well as several popular peer to peer applications [1, 14] TerraDir di ers from these systems in its exibility and decentralization. INS also allows anycasting, i.e. indirect addressing by attributes. TerraDir is not a transport layer service, but could easily be extended in this direction. ....

P. Wycko, S. McLaughry, T. Lehman, D. Ford, and T. Spaces. Ibm systems journal, 1998.

....for initiating context queries. 6.3. Service Infrastructures A service infrastructure is middleware that makes it easy to create and offer network accessible services. Examples of service infrastructures include Jini [23] Salutation [5] Hewlett Packard s eSpeak [15] Ninja [11] IBM TSpaces [30], and Interactive Workspaces [10] I plan to build Context Fabric on top of one of these service infrastructures but have not decided which one at this point. 6.4. Automatic Path Creation Previous research on Automatic Path Creation has focused on network protocol and data format ....

....interfaces so that others can create more sophisticated components. Areas currently not planned to be covered include: Building a new service infrastructure. There are many service infrastructures being developed, such as Jini [23] Salutation [5] HP eSpeak [15] Ninja [11] and IBM Tspaces [30]. I plan on using one of these and building the Context Fabric infrastructure on top. Building a massively scalable infrastructure. At this point, I feel it is more important to get the interfaces, abstractions, and principles right before addressing the scaling issues. Developing new kinds ....

Wykoff, P., S.W. McLaughry, T.J. Lehman, and D.A. Ford, TSpaces. IBM Systems Journal, 1998. 37(3).

....approaches to coordination deploy a coordination language during coding stages of system development; i.e. coordination languages have typically been programming languages as well. Some popular coordination languages of this nature include Linda [CG89] JavaSpaces [Sun98] and TSpaces [WMLF98] GCCS, on the other hand, is intended primarily as a design language. For several reasons, however, this di erence is not as large as it may rst seem. First, as mentioned above, any language with a GCCS compatible operational semantics can be incorporated into the GCCS coordination framework; ....

P. Wycko, S. W. McLaughry, T. J. Lehman, and D. A. Ford. TSpaces. IBM Systems Journal, 37(3), 1998.

....builds upon, and they can be replaced with other equivalent components. The EventHeap [5] is a flexible event based communication system used by all iRoom applications. The EventHeap is conceptually based on the tuplespace blackboard model espoused by LINDA [1] and is implemented using IBM TSpaces [20]. Processes post events to the shared EventHeap and can subscribe to events matching a specified pattern. The Context Memory [22] is an XML based lightweight datastore for storing workspace context information. Submitted to Ubicomp2001 DRAFT Do not distribute without permission (a) Overall ....

P. Wycko#, S. McLaughry, T. Lehman, and D. Ford. TSpaces. IBM Systems Journal, 37(3):454--474, 1998. 6

....foundation to deploy a Web implementation; however, Web attempts to achieve far more than just service discovery. In particular, we are also interested in providing a transactional framework where services are the basic operations and to provide fault tolerance and persistence. T Spaces [18] provide a middleware architecture with database capabilities. This approach is complementary to our approach in the sense that it addresses a number of orthogonal issues. In particular, TSpaces can be used to create a Web implementation. 9 Conclusions The web is growing exponentially, both in ....

P. Wycroft, S. W. McLaughry, T. J. Lehman, and D. A. Ford. Tspaces. IBM Systems Journal, August 1998. http://www.research.ibm.com/journal/sj/373/wycko#.html. 18

....may only be applied locally. Several pervasive computing projects have investigated the problem of information access and sharing in heterogeneous environments. IBM s TSpaces enhances the concept of a Tuplespace by adding consideration for heterogeneity of devices, scalability, and persistence [39]. TSpaces allow distributed applications to share information in a decoupled manner and allows a high degree of interoperability, via tuples. Their implementation includes support for access control, event noti cation, and ecient retrieval of information. In addition, new operators may be ....

P. Wycko, S. W. McLaughry, T. J. Lehman, and D. A. Ford. T Spaces. IBM Systems Journal, August 1998.

....both concurrency control and reliability across failures. However, object stores are optimized for storing heterogeneous objects and for maintaining the relationships between them, and not for storing large collections of homogeneous records. Tuple spaces, such as JavaSpaces [15] and T Spaces [47], are emerging as a new kind of network service. A tuple space stores objects and supports three basic operations: write (to add an object) read (to return a copy of an object that matches a template) and take (to remove and return an object that matches a template) While tuple spaces support ....

P. Wycko, S. W. McLaughry, T. J. Lehman, and D. A. Ford. T Spaces. IBM Systems Journal, 37(3):454-474, 1998.

No context found.

P. Wycko#, S. W. McLaughry, T. J. Lehman, and D. A. Ford. T Spaces. IBM Systems Journal, 37(3):454-- 474, 1998.

No context found.

P. Wycko#, S.W. McLaughry, T.J. Lehman, and D.A. Ford. T spaces. IBM Systems Journal, 37(3), april 1988.

No context found.

P.Wycko, S.W.McLaughry, and D.A.Ford. TSpaces. IBM System Journal, August 1998.

No context found.

P. Wycko, S.W. McLaughry, and D.A. Ford. TSpaces. IBM System Journal, August 1998. 17

No context found.

P. Wycko#, S. McLaughry, T. Lehman, and D. Ford. TSpaces. IBM Systems Journal, 37(3):454--474, 1998. 6

No context found.

P. Wycko#, S. McLaughry, T. Lehman, and D. Ford. TSpaces. IBM Systems Journal, 37(3):454--474, 1998.

No context found.

P. Wycko#, S. McLaughry, T. Lehman, and D. Ford. TSpaces. IBM Systems Journal, 37(3):454--474, 1998.

No context found.

P. Wycko, S. McLaughry, T. Lehman, and D. Ford. T Spaces. IBM Systems Journal, August 1998.

First 50 documents

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