Retained mode

This article does not cite any references or sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (March 2009)

Please help improve this article by expanding it. Further information might be found on the talk page. (February 2008)

In computing, retained mode rendering is a style for application programming interfaces of graphics libraries, in which the libraries retain a complete model of the objects to be rendered.^{[citation needed]}

Overview

By using a "retained mode" approach, client calls do not directly cause actual rendering, but instead update an internal model (typically a list of objects) which is maintained within the library's data space. This allows the library to optimize when actual rendering takes place along with the processing of related objects.^{[citation needed]}

Some techniques to optimize rendering include:^{[citation needed]}

• managing double buffering
• performing occlusion culling
• only transferring data that has changed from one frame to the next from the application to the library

Immediate mode is the opposite approach, but the two styles can coexist in the same library and are not necessarily exclusionary in practice. For example, OpenGL has immediate mode functions that can use previously defined server side objects (textures, vertex and index buffers, shaders, etc.) without resending unchanged data.^{[citation needed]}

See also

• Scene graph
• Model-view-controller