Difference between revisions of "Linden Lab Official talk:Media Rendering Plugin System Technical Overview"
Jump to navigation
Jump to search
Rand Linden (talk | contribs) (Created page with 'Current draft notes and questions: One-shot rendering mode: Not Yet Implemented Proxy Objects: LLPluginClassMedia - knows about msg defns. Does every media plugin require a sp...') |
Rand Linden (talk | contribs) m (moved Talk:Media Rendering Plugin System Technical Overview to Linden Lab Official talk:Media Rendering Plugin System Technical Overview) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Notes to integrate == | |||
Proxy Objects: LLPluginClassMedia - knows about msg defns. | Proxy Objects: LLPluginClassMedia - knows about msg defns. | ||
| Line 11: | Line 8: | ||
The API describes the interface between the plugin and the plugin manager. | The API describes the interface between the plugin and the plugin manager. | ||
This is subject to a design decision about how messages are routed - via the plugin manager or directly from plugin to client. | This is subject to a design decision about how messages are routed - via the plugin manager or directly from plugin to client. | ||
--[[User:Rand Linden|Rand Linden]] 19:22, 19 August 2009 (UTC) | |||
Latest revision as of 13:46, 4 May 2011
Notes to integrate
Proxy Objects: LLPluginClassMedia - knows about msg defns.
Does every media plugin require a special/custom proxy object? Do we expect MOST media plugins to require a custom proxy object?
"Likewise, each proxy object will have a mechanism (probably a listener-type interface) that will allow other code to sign up to receive relevant messages from the plugin. "
The API describes the interface between the plugin and the plugin manager. This is subject to a design decision about how messages are routed - via the plugin manager or directly from plugin to client.
--Rand Linden 19:22, 19 August 2009 (UTC)