| N. Sample, D. Beringer, L. Melloul, and G. Wiederhold. "CLAM: Composition Language for Autonomous Megamodules," Proceedings of the 3rd International Conference on Coordination Models and Languages, Amsterdam, Netherland, pp. 291-306, 1999. |
....we also translate services to isolate the side e#ect part. Reasoning about side e#ects is a necessary precondition to apply our technique to other languages. Sample et al. argue that even more information should be used for composition, like cost, associated network delay, or security requirements [6]. In order to script external components, they have to imported into the composition environment first. The tool SWIG [2] automatically generates wrappers in C to script components written in C and C in Perl, Tcl, or Python. Making components available in Piccola can be done generically since ....
N. Sample, D. Beringer, L. Melloul, and G. Wiederhold. CLAM: Composition language for autonomous megamodules. In P. Ciancarini and A. Wolf, editors, Proceedings of Coordination'99, LNCS 1594, pages 291--306, 1999.
....3. Actions can be enabled or disabled. 4. Actions can be composed with synchronization policies. 5. Actions have no result. Therefore we need also queries. Queries can block, but they must not invoke any actions. An example for a composition language with builtin (high level) services is CLAM [14]. In this language, service estimate their invocation costs, can complete partially, and can be invoked synchronous or asynchronous. Each action has a well defined effect [REF Effect system, Talpin] The composition with synchronization policies also provides means to have pluggable transactions ....
Neal Sample, Dorothea Beringer, Laurence Melloul and Gio Wiederhold, "CLAM: Composition Language for Autonomous Megamodules," Proceedings of Coordination'99, LNCS 1594, Paolo Ciancarini, Alexander L. Wolf (Ed.), 1999, pp. 291-306.
....[15] is echoed in the megaprogramming framework [5, 25] which builds on software components called megamodules [18] that capture the functionality of autonomous services provided by large organizational units. Autonomous services are linked together according to composition specifications [19, 23] to form megaservices. We use the term autonomous services to describe the cooperating service components and emphasize their common characteristics. First, autonomous services are usually computational or data intensive, involving long running processes that desire asynchronous invocations. ....
....service composition system that is based on the concept of megaprogramming. It focuses on the composition of services that are provided by large, distributed components. CHAIMS provides a practical generalpurpose compositional language. A purely compositional language CLAM has been defined in [19] to provide the application programmers the necessary abstractions to describe the behaviors of their megaprograms. CHAIMS also provides a runtime environment to hide heterogeneity in the underlying systems. The megaservice execution model is similar to that of Idealized Worker Idealized Manager ....
[Article contains additional citation context not shown here]
N. Sample, D. Beringer, L. Melloul, and G. Wiederhold, "CLAM: Composition Language for Autonomous Megamodules", Proceedings of Third International Conference on Coordination Models and Languages, Amsterdam, April 1999.
....provides key language primitives that enable dynamic scheduling with the possibility of recovery from hazards. CLAM contains a primitive to get estimates of the job completion time and cost from a service provider (ESTIMATE) and a primitive to examine job progress from a service provider (EXAMINE)[16]. These two capabilities used in concert allow for scheduling a program with more confidence in execution time. Other coordination languages such as MANIFOLD are appropriate for this type of composition, but lack the EXAMINE and ESTIMATE primitives found in CLAM [17,18] The current supported ....
....programs, workflows, etc. 5,19,22,23] Within CHAIMS, megaprograms are composed from megamodules. Megamodules are what we have referred to simply as services; they are assumed to possibly come from multiple programming languages, distinct hosts, and have different native distribution protocols [16]. An initial objective of CHAIMS was to simply develop a language and runtime support for the programs composed from distributed modules. The focus of this work is to add a dynamic scheduler to the system that can deal with the issues that arise in an unreliable environment. We build on their ....
[Article contains additional citation context not shown here]
N. Sample, D. Beringer, L. Melloul and G. Wiederhold, "CLAM: Composition Language for Autonomous Megamodules," Third Int'l Conference on Coordination Models and Languages, COORD'99, Amsterdam, April 26-28, 1999.
....of the traditional call model has been discussed for some time [10] we advocate a further breakdown of the extraction phase of this model. We propose an extraction model, developed in the course of research and development of the language CLAM (Composition Language for Autonomous Megamodules) [8] within the CHAIMS (Composing High level Access Interfaces for Multisite Software) megaprogramming project [1] which encompasses these three important augmentations (asynchronous, partial, progressive) to RPC style result extraction models. The amalgamation of these three extraction paradigms ....
....methods have potentially more value in the context of computational services than in the context of data services. We present CLAM as one possible language and implementation of our generic result extraction model. CLAM is a composition language, rather than computationally oriented language [8, 14]. As such, it is aptly suited to the presentation of this extraction model, though not necessarily a programmer s language of choice for a given problem. We advocate this extraction model here, and present it within a particular working framework (CHAIMS) Our model is client centric because, ....
[Article contains additional citation context not shown here]
N. Sample, et al., CLAM: Composition Language for Autonomous Megamodules, Third Int'l Conference on Coordination Models and Languages, COORD'99, Amsterdam, April 26-28, 1999 (Springer LNCS).
....of the traditional call model has been discussed for some time [10] we advocate a further breakdown of the extraction phase of this model. We propose an extraction model, developed in the course of research and development of the language CLAM (Composition Language for Autonomous Megamodules) [8] within the CHAIMS (Composing High level Access Interfaces for Multisite Software) megaprogramming project [1] that encompasses these three important augmentations (asynchronous, partial, progressive) to RPC style result extraction models. The amalgamation of these three extraction paradigms ....
....requests for both. We specifically contrast this client centric approach to the CORBA event model seen in 3.4. Finally, we present CLAM as one possible language and implementation of our generic result extraction model. CLAM is a composition language, rather than computationally oriented language [8, 14]. As such, it is aptly suited to the presentation of this extraction model, though not necessarily a programmer s language of choice for a given problem. We advocate this extraction model here, and present it within a particular working framework (CHAIMS) 2.2 Language specification In CLAM, ....
[Article contains additional citation context not shown here]
N. Sample, D. Beringer, L. Melloul and G. Wiederhold: "CLAM: Composition Language for Autonomous Megamodules," Third Int'l Conference on Coordination Models and Languages, COORD'99, Amsterdam, April 26-28, 1999 (Springer LNCS).
....The distribution protocol used during a specific communication between the client and a remote server is the one of the server itself, and must be supported by the client. In the context of CHAIMS, the composer writes a simple megaprogram in CLAM (CHAIMS Language for Autonomous Megamodules) [10], a composition only CPAM, A Protocol for Software Composition 15 language. This program contains the sequence of invocations to the megamodules the composer wishes to compose (an example of megaprogram is given in section 5.3) The CHAIMS compiler parses the megaprogram and generates the whole ....
N. Sample, D. Beringer, L. Melloul and G. Wiederhold: "CLAM: Composition Language for Autonomous Megamodules"; Third Int'l Conference on Coordination Models and Languages, COORD'99, Amsterdam, April 26-28, 1999
No context found.
N. Sample, D. Beringer, L. Melloul, and G. Wiederhold. "CLAM: Composition Language for Autonomous Megamodules," Proceedings of the 3rd International Conference on Coordination Models and Languages, Amsterdam, Netherland, pp. 291-306, 1999.
No context found.
N. Sample, D. Beringer, L. Melloul, G. Widerhold, Clam: Composition language for autonomous megamodules, in: Coordination Languages and Models - COORDINATION'99, Vol. 1594 of LNCS, Springer-Verlag, (1999).
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