plugins run in the memory space of dcerouter
As I understand it I can compile any plug-in as a DCE device.
see wiki Developers_Guide#3._DCERouter
Plug-inís are DCE Devices that run within the DCERouter's memory space. They are DCE Devices just like any other and they are created like any other DCE Device. The code is the same, it's just a compilation option whether the device is built as a normal DCE Device, which runs in its own memory space and communicates with DCERouter over a socket, or if it's a plug-in which gets loaded into DCERouter's memory space.
i dont understand what this approach is intended to solve though either...
Low power core -> less electricity use.
even standard pc hardware can be made fairly low power
but my idea is so keep the media section more separate as this seems to have the highest cpu requirement, keep all the big hds TV cards e.t.c in a primary media detector that will be woken over lan should another media director be started. Most of the time media items will not be needed so I can keep the more powerful pc off.
Anyone have any idea about the cpu requirements per camera / how it scales?