Quarterware for middleware

Singhai, Ashish; Sane, Aamod; Campbell, Roy H.

doi:10.1109/icdcs.1998.679502

Cited by 33 publications

(16 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This early reflective middleware platform supports multiple middleware standards, including CORBA, Java RMI, and MPI [11]. It uses a component framework in which the various ORB mechanisms are realized in terms of components.…”

Section: Hides the Detailsmentioning

confidence: 99%

The case for reflective middleware

Costa²,

et al. 2002

View full text Add to dashboard Cite

R ecent advances in distributed, mobile, and ubiquitous systems demand new computing environments characterized by a high degree of dynamism. Variations in resource availability, network connectivity, and hardware and software platforms influence the performance of the related user applications. The expected growth of ubiquitous computing over the next five years will further alter the nature of the computational infrastructure, bringing a plethora of small devices and requiring customized protocols and policies to fulfill users' evolving quality of service (QoS) requirements.During the past 10 years, software developers created middleware technology to facilitate development of software systems, most notably distributed and Internet-based, to support activities as diverse as scientific computation, information discovery and dissemination, and e-commerce. Middleware mediates interaction between the application and the operating system (hence its name). Related technologies, including the Object Management Group's CORBA, Sun Microsystems' Java-based J2EE, and Microsoft's .NET, hide from the pro-grammer the complicated details of network communication, remote method invocation, naming, and service instantiation, easing construction of complex distributed systems. CORBA, or Common Object Request Broker Architecture, and Java also hide the differences in the underlying software and hardware platforms, increasing portability and facilitating maintenance, as new versions of operating systems are released. Despite aiding development of distributed applications, conventional middleware technology lacks support for the dynamic aspects of the new computational infrastructure. Next-generation applications require middleware that can be adapted to changes in the environment and customized to fit into devices, from PDAs and sensors to powerful desktops and multicomputers [1,5]. Here, we reflect on how two independent research projects might influence the evolution of next-generation middleware. The reflective middleware model is a principled and efficient way of dealing with highly dynamic environments yet supports development of flexible and adaptive systems and applications.It's flexible and reconfigurable yet simple for programmers to use, notably for building dynamic distributed applications operating on the Net.

show abstract

Section: Hides the Detailsmentioning

confidence: 99%

The case for reflective middleware

Costa²,

et al. 2002

View full text Add to dashboard Cite

show abstract

“…This accounted not only for TNPnon-reactive but also for TNP-reactive B ceils. The finding thai ihe expanded population of TNP-specific B cells in prenataily tolerized mice displayed a similar degree of idiotypie connectivity as naturally activated B celts of prenatally untreated mice could well be interpreted in the sense that tolerance at the B-cell level, at least partly, may be a consequence of preserved idiotypie connectivity despite contact with the tiominal antigen [48].…”

Section: Discussionmentioning

confidence: 97%

Alteration of Idiotypic Connectivity in Prenatally Tolerized Neonatal Mice*

Zöller

1990

Scand J Immunol

View full text Add to dashboard Cite

Prenatal tolerization with trinitrobenzenesulphonic acid (TNBS) leads to expansion of trinitrophenyl (TNP)-specific B cells, the majority of which become refractory to stimulation during postnatal development. One possible explanation could be that they belong to the repertoire of naturally activated B cells which are limited in expansion after antigenic stimulation due to a high degree of idiotypic connectivity. To evaluate this hypothesis, 59 thymus- and 490 spleen-derived B-cell hybridomas from 6-day-old prenatally untreated and prenatally TNBS-treated mice were tested for reactivity against 33 arbitrarily chosen clones derived from the same fusions, 17 being derived from control and 16 from tolerized litters. Two major points could be deduced: (1) Idiotypic connectivity, including connectivity of TNP- and anti-TNP-reactive monoclonal antibodies (MoAb), was maintained after prenatal tolerization. This accounted for thymus- and spleen-derived MoAb. (2) Only TNP- and anti-TNP-reactive MoAb derived from prenatally untreated and prenatally tolerized mice displayed significantly distinct idiotypic profiles. Differences were pronounced, especially with thymus-derived MoAb. Thus, TNP-specific B cells in prenatally tolerized newborns do not behave like B cells of adult mice stimulated by external antigen, but rather like a part of the naturally activated, idiotypically connected B-cell repertoire of the newborn. This could explain B-cell unresponsiveness at older age as a consequence--at least partly--of their high idiotypic connectivity.

show abstract

“…However, reflective middleware systems often provide low level APIs and introduce non-marginal performance and memory overheads. Systems such as Quarterware [22] and Arcademis [17] rely on the concept of frameworks. These systems provide semi-complete platforms that can be extended and personalized by middleware users.…”

Section: Aspectjrmi (A) Jacorb (B) a / Bmentioning

confidence: 99%

An Aspect-Oriented Communication Middleware System

Valente

Tirelo

Leao

et al. 2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. This paper describes a Java-based communication middleware, called AspectJRMI, that applies aspect-oriented programming concepts to achieve the following requirements: (1) modular implementation of its features, including those with a crosscutting behavior; (2) high degree of configurability and adaptability; (3) performance similar to conventional object-oriented communication middleware systems, such as CORBA and Java RMI. In AspectJRMI, users may explicitly select the features provided by the middleware infrastructure, according to their needs. Most of these features have a crosscutting behavior, including interceptors, oneway calls, asynchronous calls, value-result parameter passing, and collocation optimizations. In this case, they are implemented as aspects. The design of AspectJRMI follows a set of principles, called horizontal decomposition, to achieve pluggability of aspects to the core middleware implementation. This paper presents the programming interface and the implementation of AspectJRMI. It also presents experimental results of its performance.

show abstract

Quarterware for middleware

Cited by 33 publications

References 10 publications

The case for reflective middleware

The case for reflective middleware

Alteration of Idiotypic Connectivity in Prenatally Tolerized Neonatal Mice*

An Aspect-Oriented Communication Middleware System

Contact Info

Product

Resources

About