-
|
Hello, I would like to ask, whether it would make sense to provide access to the NMOS flow definition used to create the flow somehow "internally" to MXL, or whether it is always expected that this type of information will be passed through some external side channel? For example, the definition contains information like frame width, frame height and other data which may be useful for the readers of the flow. If the NMOS definition was available from the MXL directly, it would allow readers to just be supplied with the domain and the flow ID and the rest of the information they could get from MXL directly. But maybe that would be seen just as unnecessary complication and supplementing functionality which is supposed to be provided by external flow discovery mechanism? Opinions? Has this been discussed before? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Are you suggesting something like mxlGetFlowDescriptor(mxlReader*... , const char* id....); |
Beta Was this translation helpful? Give feedback.
Closing discussion, will be resolved under issue #102.