[Bug 709117] souphttpsrc: Need ability to exclude HTTP Range header and set content size

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=709117
  GStreamer | gst-plugins-good | 1.x

--- Comment #13 from Sebastian Dröge (slomo) <slomo at circular-chaos.org> 2013-10-07 14:18:43 UTC ---
(In reply to comment #12)
> The dlnasrc element needs to be used both inside and outside of the WebKit
> framework.  There is another gstreamer based media player which is built within
> the Rygel framework that also needs the dlnasrc element.
> 
> It sounds like the cookie and authentication logic is built within the WebKit
> framework and not GStreamer.  I imagine it would not be easy to move it to the
> gstreamer framework.  Sounds like it will need to be duplicated in GStreamer?

Yes

> In terms of your comment - "work with any HTTP source element that provides a
> specific interface", can you give an example of what you meant by "specific
> interface"?  

The properties and signals on the element, the behaviour it provides. So you
could have the same dlnasrc element that can use souphttpsrc or webkitwebsrc
without having to worry about what the exact HTTP element is that is used.

> Thinking in terms of implementation, the media player's pipeline source would
> determine this is a "dlna" server so I need to utilize the "dlna" interface and
> include HTTP headers which are specific to dlna.  Or this is an icecast server,
> so I need to utilzie the "icecast" interface and include the ice HTTP headers. 
> Is that what you were thinking?

That's not what I thought but that's also an interesting idea about how we
could define some kind of interface for HTTP elements. Or some helper API on
top of that interface which sets specific HTTP headers for example.

-- 
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.