While I was looking into ticket 10380 I thought about ways of making plugin execution more reliable.
The isPlayable property is important to decide if the plugin needs a handle or not. Calling a isPlayable plugin without a handle will break setResolvedUrl(), calling a normal plugin with a handle will kill script execution after a timeout. Yet, properties might get lost along the way (see CGUIWindowVideoInfo:
lay()) or cannot be set in some cases (e.g. JSON-RPC).
My idea is to introduce a new protocol, say urlplugin://, to replace the isPlayable property. That way you are able to toss the URL around all the way you want and in the end, still be able to determine how to execute the plugin.
So before I start spending my time on writing a patch I wanted to know what you guys think of it and make sure it is not a no go to begin with.
The isPlayable property is important to decide if the plugin needs a handle or not. Calling a isPlayable plugin without a handle will break setResolvedUrl(), calling a normal plugin with a handle will kill script execution after a timeout. Yet, properties might get lost along the way (see CGUIWindowVideoInfo:
lay()) or cannot be set in some cases (e.g. JSON-RPC).My idea is to introduce a new protocol, say urlplugin://, to replace the isPlayable property. That way you are able to toss the URL around all the way you want and in the end, still be able to determine how to execute the plugin.
So before I start spending my time on writing a patch I wanted to know what you guys think of it and make sure it is not a no go to begin with.
