[Bug 738298] souphttpsrc: add 'pause-mode' property

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=738298
  GStreamer | gst-plugins-good | unspecified

--- Comment #4 from Guillaume Desmottes <gdesmott at gnome.org> 2014-10-13 10:13:42 UTC ---
(In reply to comment #3)
> I think this should only be done if accept-ranges is declared by the server,

This makes sense for the "pure" HTTP use case but is going to be problematic
when using the dlnasrc element. DLNA defines its own HTTP field for servers to
advertise that they support "byte range" (see "7.5.4.3.2.22 MT HTTP header:
Range (server)" in the spec). Some servers (like the MCVT tool) only use this
field so we wouldn't be able to use "pause range" on those.

Also, in theory, a DLNA server could support only "time range" requests (which
is DLNA specific) so we'd still want to be able to support "time pause" in that
case.

This behaviour won't be the default anyway, so maybe we could argue that if you
enable it through a property you are supposed to know if the server is going to
support it or not?

> and also disconnecting should probably wait a little bit. Like only disconnect
> if you're in paused for >10 seconds.

Yeah that's what I suggested by having a 'pause-timeout' property instead.

> Independent of that you should not look at the pipeline state, but instead look
> if downstream is blocked. Data processing happens (and should!) in paused.

Do you mean I shouldn't catch the state change in
gst_soup_http_src_change_state()? What's the proper way to know if the src pad
is accepting data or not?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.