[Webkit-unassigned] [Bug 34003] [GTK] Pass cookies to GStreamer

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 22 10:03:14 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=34003


Dan Winship <danw at gnome.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |danw at gnome.org




--- Comment #7 from Dan Winship <danw at gnome.org>  2010-01-22 10:03:14 PST ---
(In reply to comment #5)
> Dan Winship told me yesterday that another solution would be to copy the webkit
> soup session and hand it to gstreamer.
> 
> I believe this solution would be more future-proof, because at some point we
> will need more context: referrer, auth/ssl, proxy (not sure if it's relevant
> for webkit/gnome, but that's the idea)...

and also, then if the server response with a redirection, you can look up the
right cookies for the new host, instead of continuing to send the cookies for
the old host...

(I don't know if that's relevant in practice... I can imagine something like a
video.google.com URL redirecting to youtube.com though...)

(In reply to comment #6)
> Problem with this is, that SoupSession is not threadsafe unfortunately

(SoupSession*Async* that is.) Ah, yes, there is that. Or more importantly, it
can only have a single GMainContext, and IIRC souphttpsrc wants to set its own
GMainContext on the session so that it control when I/O is and isn't happening.
(The libsoup i/o rewrite / gio-ification might solve this problem.)

It's possible you could share SoupSessionFeatures (cookie jar, proxy URI
resolver, etc), without sharing the whole session. Some of them might not
currently be thread-safe, but they could be fixed.

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



More information about the webkit-unassigned mailing list