D. C. Schmidt and C. Cleeland, "Applying a Pattern Language to Develop Extensible ORB Middleware," in Design Patterns in Communications (L. Rising, ed.), Cambridge University Press, 2000.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....networking resources) provides the middleware technology that is most well suited for QoSenabled DRE systems, our work (and Section 3 in this paper) focuses on CCM. Although each of these component models differ from each other, there are key similarities, particularly in terms of their patterns [24, 25]. Below, we describe the most common capabilities that are shared among these component models. Multiple views per component. Each component model specifies a collection of interfaces that a component can export to its clients. These interfaces vary in the capabilities that they offer to clients. ....

D. C. Schmidt and C. Cleeland, "Applying a Pattern Language to Develop Extensible ORB Middleware," in Design Patterns in Communications (L. Rising, ed.), Cambridge University Press, 2000.

....has been designed to run solely on Palm OS platforms. It would however, be nice if the ORB could be ported to other diverse handheld devices, such as the IPAQ pocket PC. One way of extending this ORB to enable 79 cross platform portability, would involve utilising the Wrapper Facade pattern [Schmidt 99] to encapsulate low level functions and other Palm OS specific functions and data structures, with object oriented class interfaces. Wrapper facades provide methods that forward client invocations to non portable functions, so that such functions do not have to be accessed directly. See figure ....

Douglas C. Schmidt, Chris Cleeland, Applying a Pattern Language to Develop Extensible ORB Middleware, Design Patters in Communication, Cambridge University Press 2000

No context found.

D. C. Schmidt and C. Cleeland, "Applying a Pattern Language to Develop Extensible ORB Middleware," in Design Patterns in Communications (L. Rising, ed.), Cambridge University Press, 2000.

....10 Applying the solution in TAO: In TAO, the role of the protocol registry is played by the Connector Registry on the client and the Acceptor Registry on the server. This registry is created by TAO s Resource Factory,whichis an abstract factory that creates all the ORB s strategies and policies [28]. Figure 7 depicts the Connector Registry and its relation to the abstract factories. ACCEPTOR REGISTRY IIOP ATM IOP IIOP ATM IOP CONNECTOR REGISTRY CLIENT SIDE SERVER SIDE Figure 7: TAO Connector and Acceptor Registries Note that TAO does not use abstract factories directly, however. ....

.... I O subsystem integration [20] evaluation Real time CORBA [11] features [19] fault tolerance features [14, 15] reflective QoS techniques the CORBA Component Model [37] multimedia streaming support [21] systematic benchmarking of multiple ORBs [38] and patterns for ORB extensibility [28] and optimization [7] The design of TAO s pluggable protocols framework is influenced by prior research on the design and optimization of protocol frameworks for communication subsystems. This section outlines that research and compares it with our work. Configurable communication frameworks: ....

[Article contains additional citation context not shown here]

D. C. Schmidt and C. Cleeland, "Applying a Pattern Language to Develop Extensible ORB Middleware," in Design Patterns in Communications (L. Rising, ed.), Cambridge University Press, 2000.

.... a wide range of communication systems, including on line transaction processing systems, telecommunication switch management systems [4] electronic medical imaging systems [5] parallel communication subsystems [6] avionics mission computers [7] and real time CORBA object request brokers (ORBs) [8]. Although the specific application requirements in these systems were different, the communication software design challenges were similar. This pattern language therefore embodies design expertise that can be reused broadly in the domain of communication software, well beyond the gateway example ....

....connections. These events are used by the Acceptor component described in Section 3.5. The Reactor pattern has been used in many single threaded event driven frameworks, such as the Motif, Interviews [11] System V STREAMS [12] the ACE OO communication framework [9] and implementations of CORBA [8]. In addition, it provides the event demultiplexing infrastructure for all of the other strategic patterns presented below. 3.4 The Component Configurator Pattern Intent: The Component Configurator pattern allows an application to link and unlink its component implementations at run time without ....

[Article contains additional citation context not shown here]

D. C. Schmidt and C. Cleeland, "Applying a Pattern Language to Develop Extensible ORB Middleware," in Design Patterns in Communications (L. Rising, ed.), Cambridge University Press, 2000.

No context found.

D. C. Schmidt and C. Cleeland, "Applying a Pattern Language to Develop Extensible ORB Middleware," in Design Patterns and Communications, L. Rising, Ed.: Cambridge University Press, 2000.

No context found.

D. C. Schmidt and C. Cleeland, "Applying a Pattern Language to Develop Extensible ORB Middleware," in Design Patterns and Communications, L. Rising, Ed.: Cambridge University Press, 2000.

No context found.

D. C. Schmidt and C. Cleeland. Applying a Pattern Language to Develop Extensible ORB Middleware. In L. Rising, editor, Design Patterns in Communications. Cambridge University Press, 2000.

No context found.

D. Schmidt and C. Cleeland, "Applying a Pattern Language to Develop Extensible ORB Middleware," IEEE Communications Magazine, vol. 37, 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