|
|
|
|
| LEADER |
04110nmm a2200409 u 4500 |
| 001 |
EB000375399 |
| 003 |
EBX01000000000000000228451 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
130626 ||| eng |
| 020 |
|
|
|a 9783540322818
|
| 100 |
1 |
|
|a Dearle, Alan
|e [editor]
|
| 245 |
0 |
0 |
|a Component Deployment
|h Elektronische Ressource
|b Third International Working Conference, CD 2005, Grenoble, France, November 28-29, 2005, Proceedings
|c edited by Alan Dearle, Susan Eisenbach
|
| 250 |
|
|
|a 1st ed. 2005
|
| 260 |
|
|
|a Berlin, Heidelberg
|b Springer Berlin Heidelberg
|c 2005, 2005
|
| 300 |
|
|
|a X, 197 p
|b online resource
|
| 505 |
0 |
|
|a Middleware Integration -- Cooperative Component-Based Software Deployment in Wireless Ad Hoc Networks -- Infrastructure for Automatic Dynamic Deployment of J2EE Applications in Distributed Environments -- Patterns for Deployment -- Component Deployment Using a Peer-to-Peer Overlay -- A Methodology for Developing and Deploying Distributed Applications -- QOS Issues -- Crosslets: Self-managing Application Deployment in a Cross-Platform Operating Environment -- DAnCE: A QoS-Enabled Component Deployment and Configuration Engine -- Adaptability, Customisation and Format Aware Deployment -- Improving Availability in Large, Distributed Component-Based Systems Via Redeployment -- A Decentralized Redeployment Algorithm for Improving the Availability of Distributed Systems -- Dependability -- Propagative Deployment of Hierarchical Components in a Dynamic Network -- Modelling Deployment Using Feature Descriptions and State Models for Component-Based Software Product Families -- Assembly and Packaging -- J2EE Packaging, Deployment and Reconfiguration Using a General Component Model -- A Model of Dynamic Binding in .NET -- Case Studies -- Reuse Frequency as Metric for Dependency Resolver Selection -- ORYA: A Strategy Oriented Deployment Framework -- Deployment of Infrastructure and Services in the Open Grid Services Architecture (OGSA)
|
| 653 |
|
|
|a Computer systems
|
| 653 |
|
|
|a Compilers (Computer programs)
|
| 653 |
|
|
|a Computer Science Logic and Foundations of Programming
|
| 653 |
|
|
|a Compilers and Interpreters
|
| 653 |
|
|
|a Operating Systems
|
| 653 |
|
|
|a Software engineering
|
| 653 |
|
|
|a Programming Techniques
|
| 653 |
|
|
|a Computer science
|
| 653 |
|
|
|a Computer System Implementation
|
| 653 |
|
|
|a Computer programming
|
| 653 |
|
|
|a Operating systems (Computers)
|
| 653 |
|
|
|a Software Engineering
|
| 700 |
1 |
|
|a Eisenbach, Susan
|e [editor]
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b Springer
|a Springer eBooks 2005-
|
| 490 |
0 |
|
|a Programming and Software Engineering
|
| 028 |
5 |
0 |
|a 10.1007/11590712
|
| 856 |
4 |
0 |
|u https://doi.org/10.1007/11590712?nosfx=y
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 004.2
|
| 520 |
|
|
|a This volume of Lecture Notes in Computer Science contains the proceedings of the rd 3 Working Conference on Component Deployment (CD 2005), which took place from 28 to 29, November 2005 in Grenoble, France, and co-located with Middleware 2005. CD 2005 is the third international conference in the series, the first two being held in Berlin and Edinburgh in 2002 and 2004, respectively. The proceedings of both these conferences were also published by Springer in the Lecture Notes in Computer Science series and may be found in volumes 2370 and 3083. Component deployment addresses the tasks that need to be performed after components have been developed and addresses questions such as: • What do we do with components after they have been built? • How do we deploy them into their execution environment? • How can we evolve them once they have been deployed? CD 2005 brought together researchers and practitioners with the goal of deve- ping a better understanding of how deployment takes place in the wider context. The Program Committee selected 15 papers (12 long papers, three short papers) out of 29 submissions. All submissions were reviewed by at least three members of the Program Committee. Papers were selected based on originality, quality, soundness and relevance to the workshop
|