<?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="Direct Rendering Infrastructure - Page 26 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Direct_Rendering_Infrastructure&amp;p=25">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Direct_Rendering_Infrastructure&amp;p=27">3.Next</a>
</p>
<p>instead.</p>

<p>Buffer allocation on the client side breaks <a href="page.php?w=GLX">GLX</a> assumptions in the sense that it's no longer possible for multiple GLX applications to render cooperatively in the same window. On the plus side, the fact that the DRI client is in charge of its own buffers throughout their lifetime brings many advantages. For example, it is easy for the DRI3 client to ensure that the size of the render buffers always match the current size of the window, and thereby eliminate the artifacts due to the lack of synchronization</p><p>
<a accesskey="1" href="page.php?w=Direct_Rendering_Infrastructure&amp;p=25">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Direct_Rendering_Infrastructure&amp;p=27">3.Next</a>
</p>

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

</card>
</wml>
