Implement a means to create MMALSharp specific components, these should function in the same way that native ones do but are in a managed environment; these components should have the ability to be connected to other native/managed components, sending data using MMALBuffers. The managed connections should also mimic native ones - I envisage this working using the new connection callback handler functionality brought in for 0.4 and if the downstream component is managed, we can invoke its "Data processing" delegate in managed code.
Issues like this could be resolved by having a custom pipeline of native/managed components. The callback/capture handlers could be used also, but I'd like to separate concerns and provide as much flexibility as possible within MMALSharp.
techyian
commented
5 years ago
Implement a means to create MMALSharp specific components, these should function in the same way that native ones do but are in a managed environment; these components should have the ability to be connected to other native/managed components, sending data using MMALBuffers. The managed connections should also mimic native ones - I envisage this working using the new connection callback handler functionality brought in for 0.4 and if the downstream component is managed, we can invoke its "Data processing" delegate in managed code.
Issues like this could be resolved by having a custom pipeline of native/managed components. The callback/capture handlers could be used also, but I'd like to separate concerns and provide as much flexibility as possible within MMALSharp.