course_1
no way to compare when less than two revisions
Différences
Ci-dessous, les différences entre deux révisions de la page.
| — | course_1 [2010/01/17 09:57] (Version actuelle) – créée tigli | ||
|---|---|---|---|
| Ligne 1: | Ligne 1: | ||
| + | ====== Course 1 ====== | ||
| + | |||
| + | ===== Introduction ===== | ||
| + | |||
| + | ==== What does Traditional Middleware Mean ? ==== | ||
| + | |||
| + | === Motivations === | ||
| + | |||
| + | * make development faster and easier | ||
| + | |||
| + | * to assist distributed software | ||
| + | |||
| + | * promoting software reuse | ||
| + | |||
| + | * A bridge between OS and application [Krakoviak] | ||
| + | |||
| + | * High level network abstractions matching the application computational model [Issarny] | ||
| + | |||
| + | === First Definitions === | ||
| + | |||
| + | === Middleware Taxonomies === | ||
| + | |||
| + | * W. Emmerich Taxonomy (2000) | ||
| + | * D.E. Baken (2001) | ||
| + | * R. E. Schantz and D. C. Schmidt Taxonomy (2002) | ||
| + | |||
| + | == Transactional Middleware == | ||
| + | == Tuplespace-based Middleware == | ||
| + | == Message-oriented Middleware == | ||
| + | == Remote procedure Calls Middleware == | ||
| + | == Object oriented Middleware == | ||
| + | |||
| + | == Component oriented Middleware == | ||
| + | == Service-oriented Middleware == | ||
| + | |||
| + | === Exercices === | ||
| + | |||
| + | |||
| + | === References === | ||
| + | |||
| + | A Perspective on the Future of Middleware-based Software Engineering. | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | ==== What does Ubiquitous Computing Mean ? ==== | ||
| + | |||
| + | |||
| + | === Exercices === | ||
| + | |||
| + | === videos === | ||
| + | |||
| + | The following scenes together are a complete [[http:// | ||
| + | |||
| + | === References === | ||
| + | |||
| + | GATECH Course about Ubiquitous computing [[http:// | ||
| + | |||
| + | |||
| + | ==== What does Middleware for Ubiquitous Computing Mean ? ==== | ||
| + | |||
| + | === New motivations === | ||
| + | |||
| + | * High level device and ressource abstractions matching the application computational model | ||
| + | * device and ressource abstraction is often transparency in multiple access | ||
| + | * Distribution with or without nertwork ... | ||
| + | |||
| + | === Example in distributed systems === | ||
| + | |||
| + | === Example in OS and Virtual Machine | ||
| + | |||
| + | === Example in HMI === | ||
| + | |||
| + | * application computational model : widgets | ||
| + | * low level device drivers : mouse and screen | ||
| + | * Middleware : | ||
| + | |||
| + | === Example | ||
| + | |||
| + | |||
| + | ==== Trends on the future of Middleware ==== | ||
| + | |||
| + | ==== From Mobility to Ubiquity | ||
| + | |||
| + | ==== New Requirements | ||
| + | |||
| + | === Exercices === | ||
| + | |||
| + | === Projets de recherche : === | ||
| + | OpenCOM and ReMMoC Web Page, Paul Grace and Gordon S. Blair - [[http:// | ||
| + | |||
| + | ARLES Project-Team, | ||
| + | |||
| + | Project AMAZONES, Citi Lab, INSA Lyon, Frenot Stéphane, Le Mouel Frédéric | ||
| + | |||
| + | |||
course_1.txt · Dernière modification : 2010/01/17 09:57 de tigli