The Camelot library: A C language extension for programming a general purpose distributed transaction system

Bloch, Joshua

doi:10.1109/icdcs.1989.37945

Cited by 6 publications

(3 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Provide the executables for the existing applications that will be part of the new application. 3 4. Execute the stub generator to generate coercion modules tailored both to the interaction between existing applications and to the environment.…”

Section: Our Integration Approachmentioning

confidence: 99%

“…It will result in changes to the application structure re ected in the bus le, to the event transformation rules re ected in the event transformation les, to the source code for two coercion modules, and to the Make les for building those two coercion modules. map VEAR obj(point: integer [3]) to VE3D ext_obj(string('liz'); point [2]; point [1]; point[0]) } Figure 5.9: Composite interaction speci cation for the VE3D/VE2D/VEAR application using ENimble (version 2) Version 4 keeps the same con guration as in version 1 at both the con guration level and module level. It di ers in that it has a di erent set of event transformation rules.…”

Section: Versionmentioning

confidence: 99%

“…The speci cation for each existing application is already created when the application is built from scratch 3. The executable for each existing application is already created when the application is built from scratch.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Configuration-level programming of distributed applications using implicit invocation

Chen

Purtilo

Proceedings of TENCON'94 - 1994 IEEE Region 10's 9th Annual International Conference On: 'Frontiers of Computer Technology'

View full text Add to dashboard Cite

An event-based distributed application is a group of software components interacting with each other by producing events that in turn trigger the invocation of procedures. In this work, we are concerned with the technology and methods for integrating an event-based application, whether that application is being constructed from scratch or synthesized from existing systems. Developing an event-based application is a complex task for programmers, who must address several issues not found in traditional systems and, currently, must do so without much assistance. These issues include event declaration, structure, binding, and naming. Our objective is to provide the same software engineering bene ts to programmers of event-based applications as are currently provided to programmers of applications using traditional RPC or messagepassing mechanisms. In this work, we broaden the technology for integration to encompass event-based programming. A method is described for separating event interaction properties from the implementation of the application modules so that system integration can be performed using only the abstractions. Then based upon the abstract aggregate, all interface software needed to validly implement the system can be generated automatically. A software bus model has been enhanced to accommodate the models which drive event-based distributed applications. In this way, designers may de ne complex event-based interactions abstractly, thus making it easier to integrate and experiment with event-based distributed applications.

show abstract

Section: Our Integration Approachmentioning

confidence: 99%