GNOME Bugzilla – Bug 577637
[playbin2] expose temp-location property
Last modified: 2009-07-13 13:52:31 UTC
The properties from queue2 should be exposed in playbin2, so that applications can set a temporary location for the file.
Setting as a blocker as per Edward's request.
In fact I was wrong in the explanation, there's only one property that needs exposing : temp-location ("Location of a temporary file to store data in"). That temporary location will disappear once queue2 (through playbin2) is set back to READY.
Do you want to do this right now? it does not work quite right yet in all cases.
Even if the implementation is a little buggy, it might be worth exposing the API already - as long as you think it's the right API. Unless the behaviour is *completely* broken and unusable, then I'd hold off.
As discussed in GCDS, I've add a flag to playbin2 to enable the progressive download feature. uridecodebin will then only enable progressive download for video/quicktime and video/x-flv media type. uridecodebin will also allocate the temp name template based on g_get_tmp_dir and the application name. Using the deep-notify one can get a handle to the allocated filename and do something with it. When playbin2 is set to READY, the file is automatically deleted.