Ravi,
It sounds like you are suggesting a private modification of OpenCore.
Is that correct? If I modify my copy of the download manager to pass
the queryInterface, then the modification will need to be reinstated
each time there is a new release of opencore that changes the download
manager. I
- As of today, we did not see a necessity for the parser nodes to
implement the PVMFDataSourceNodeRegistryInitInterface interface.
Hence, you don't see it.
- In your pipeline, strictly speaking, the download manager is the
source node. Now, what you are trying to do is to retain the source
node
Ravi,
I think what GeorgeC is trying to say is that in a multi-node
pipeline, the query for the PVMFDataSourceNodeRegistryInitInterface is
not propagated beyond the initial source node. For example, while the
download manager implements the
PVMFDataSourceNodeRegistryInitInterface, it does not send
You can still follow the same procedure and make your master node
(e.g., downloadmanager node) pass it's queryinterface downstream to
the slave node (e.g., parser node) instead of the master node itself
responding to the request.
-Ravi
On Jan 11, 12:48 am, jeffb jeffbo...@gmail.com wrote:
Ravi,
If your node implements the interface
PVMF_DATA_SOURCE_NODE_REGISRTY_INIT_INTERFACE_UUID (class
PVMFDataSourceNodeRegistryInitInterface), then even your node will be
given access to iPlayerNodeRegistry.
-Ravi
On Jan 7, 2:49 am, George C georgec2...@gmail.com wrote:
Ravi,
Thanks for your
Ravi,
Thanks for your replay. Related to external access subject: if I need
to create dynamically (during execution) a node (such as a parser
node) I need to have access to iPlayerNodeRegistry-CreateNode(..). I
noticed that the access to the iPlayerNodeRegistry is given only to
In any given shared library, only a few symbols are visible
externally. These symbols are marked with OSCL_IMPORT_REF/
OSCL_EXPORT_REF. So, you should check if the function that you are
referencing is being exported or not.
-Ravi
On Dec 16, 5:28 am, George C georgec2...@gmail.com wrote:
Ravi,
