| Namur, Belgium |
| April 20-23, 2005 |
Jayadev Misra
Title of the talk at Coordination'05 : A programming model for wide-area computing Abstract: The computational pattern inherent in many wide-area applications is this: acquire data from one or more remote services, calculate with these data, and invoke yet other remote services with the results. Additionally, it is often required to invoke alternate services for the same computation to guard against service failure. It should be possible to repeatedly poll a service until it supplies results which meet certain desired criteria, or to ask a service to notify the user when it acquires the appropriate data. And it should be possible to download an application and invoke it locally, or have a service provide the results directly to another service on behalf of the user. We introduce site as a general term for a basic service. A web service is a site. More generally, a distributed transaction, which can be regarded as an atomic step of a larger computation, is a site. We call the smooth integration of sites orchestration, and Orc is our theory of orchestration of sites. Orchestration requires a better understanding of the kinds of computations that can be performed efficiently over a wide-area network, where the delays associated with communication, unreliability and unavailability of servers, and competition for resources from multiple clients are dominant concerns. Toby Lehman
Title of the talk at Coordination'05 : Whither Coordination Systems: Lessons Learned from the TSpaces Project Abstract: When TSpaces was released to the public in 1998, we were excited with all of the possible directions it could take. This model of interaction, the Tuplespace model, featuring asynchronous and anonymous communication, was a natural fit for distributed computing. Coupled with the Java Programming Language, TSpaces could run anywhere and link together just about anything together: any device, any program, or any service. Also, Pervasive Computing was just taking off, and the explosion of portable devices (e.g. PDAs, sensors, smart phones, smart pagers) combined with the development of software services, made it seem that coordination middleware was going to be the new golden child of computing. Thrilled with this prospect, we built or designed many different types of prototypes to demonstrate the power of a coordination middleware system. Eight years, and many Tuplespace-oriented products, projects, or prototypes later, we've validated the underlying model. However, Tuplespace systems, though known and used, are not ubiquitous. They are not included in every copy of MS Windows or Linux (even though there are many who feel they should be). What happened? In this talk I will give some of the history of the TSpaces project at the IBM Almaden Research Center. I'll describe some of the systems we built on top of TSpaces and discuss their interesting aspects. Then I'll switch gears and talk about the successes and failures of Tuplespace systems, and where I believe the future lies for this under-rated field. |