Skip to content
Snippets Groups Projects
  • George Kiagiadakis's avatar
    7a486f1f
    impl-node: subclass from GObject · 7a486f1f
    George Kiagiadakis authored
    By mistake, WpImplNode was developed by keeping in mind that the proxy
    returned by pw_core_export() is a PW_TYPE_INTERFACE_Node, but this
    is not true. It's actually a ClientNode...
    
    Unfortunately, making WpImplNode work as if it was a WpNode is
    not so easy, especially when it comes to handling params, which
    need to be queried syncrhonously on the underlying spa_node.
    
    So, instead of fixing WpImplNode to work as a WpNode, we choose to
    disconnect them. This way, WpImplNode will not be used as a proxy
    in the registry and the registry will normally create WpNode proxies
    instead, making round-trips through the server to change node params.
    7a486f1f
    History
    impl-node: subclass from GObject
    George Kiagiadakis authored
    By mistake, WpImplNode was developed by keeping in mind that the proxy
    returned by pw_core_export() is a PW_TYPE_INTERFACE_Node, but this
    is not true. It's actually a ClientNode...
    
    Unfortunately, making WpImplNode work as if it was a WpNode is
    not so easy, especially when it comes to handling params, which
    need to be queried syncrhonously on the underlying spa_node.
    
    So, instead of fixing WpImplNode to work as a WpNode, we choose to
    disconnect them. This way, WpImplNode will not be used as a proxy
    in the registry and the registry will normally create WpNode proxies
    instead, making round-trips through the server to change node params.