<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Message-oriented middleware - Page 17 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=message-oriented_middleware&amp;p=16">1.Previous</a><br />
<a accesskey="3" href="page.php?w=message-oriented_middleware&amp;p=18">3.Next</a>
</p>
<p>until the resources needed to handle this work are depleted and the called component fails. Of course, these conditions can be minimized or avoided by monitoring performance and adjusting message flow, but this is work that is not needed with a synchronous messaging system. The important thing is to understand the advantages and liabilities of each kind of system. Each system is appropriate for different kinds of tasks. Sometimes, a combination of the two kinds of systems is required to obtain the desired behavior.</p>

<p><big>Standards</big></p>
<p>Historically,</p><p>
<a accesskey="1" href="page.php?w=message-oriented_middleware&amp;p=16">1.Previous</a><br />
<a accesskey="3" href="page.php?w=message-oriented_middleware&amp;p=18">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
