<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Evans, Huw</style></author><author><style face="normal" font="default" size="100%">Peter Dickman</style></author><author><style face="normal" font="default" size="100%">Malcolm Atkinson</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The GRUMPS Architecture: Run-time Evolution in a Large Scale Distributed System</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the Workshop on Engineering Complex Object-Oriented Solutions for Evolution (ECOOSE), held as part of OOPSLA 2001.</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2001</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://research.nesc.ac.uk/files/The%20Grumps%20Architecture%20-%20Run-time%20Evolution%20in%20a%20Large%20Scale%20Distributed%20System.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">This paper describes the first version of the distributed programming architecture for the Grumps1 project. The architecture consists of objects that communicate in terms of both asynchronous and synchronous events. A novel three-level extensible naming scheme is discussed that allows Grumps developers to deploy systems that can refer to entities not identified at the time when the Grumps system and application-level code were implemented. Examples detailing how the topology of a Grumps system may be changed at run-time and how new object implementations may be distributed during system execution are given. The separation of policy from mechanism is shown to be a major part of how system evolution is supported and this is made even more flexible when expressed through the use of Java interfaces for crucial core concepts.</style></abstract></record></records></xml>