<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">N. Carvalho</style></author><author><style face="normal" font="default" size="100%">José Pedro Oliveira</style></author><author><style face="normal" font="default" size="100%">José Orlando Pereira</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evaluating Throughput Stability of Protocols for Distributed Middleware</style></title><secondary-title><style face="normal" font="default" size="100%">On the Move to Meaningful Internet Systems: OTM 2009</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">600–613</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;Communication of large data volumes is a core functionality of distributed systems middleware, namely, for interconnecting components, for distributed computation and for fault tolerance. This common functionality is how- ever achieved in different middleware platforms with various combinations of operating system and application level protocols, both standardized and ad hoc, and including implementations on managed runtime environments such as Java.&lt;br /&gt;
In this paper, in contrast with most previous work that focus on performance, we point out that architectural and implementation decisions have an impact in throughput stability when the system is heavily loaded, precisely when such sta- bility is most important. In detail, we present an experimental evaluation of several communication protocol components under stress conditions and conclude on the relative merits of several architectural options.&lt;/p&gt;
</style></abstract></record></records></xml>