Provide feedback about buffering progress

[hadess]

The source should provide information about the progress maybe when setting up the Bittorrent stream, such as when it's gathering information about peers, when it's actually downloading information.

[turran]

I'm not sure if it makes sense to send buffering information when the btsrc element is transforming the magnet uri into a torrent file, at the end the async change state to paused (the prerolling) is exactly for that: the src will not start working until it can transform the data.

[hadess]

Buffering information, maybe not, but the source(s) could have source specific signals, which the front-end could use. In bug #4 for example, the progress stays stuck at 0%. If I knew that, for example, we were waiting for other users to start seeding the film, or trying to contact the tracker, etc. it might help with long operations becoming more bearable.

[turran]

I understand, it indeed makes sense. I could create a signals for different moments of the torrent negotiation/processing so the app can adapt. Also a way to get the torrent status would be nice, maybe using a Glib's action-signal and the message serialized as a GstStructure