[gstreamer-bugs] [Bug 312114] New: gnomevfssrc unneccessarily registers callbacks with gnome-vfs in some cases

[bugzilla-daemon at bugzilla.gnome.org]

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=312114
 GStreamer | gst-plugins | Ver: 0.8.10

           Summary: gnomevfssrc unneccessarily registers callbacks with
                    gnome-vfs in some cases
           Product: GStreamer
           Version: 0.8.10
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: cschmidt2 at emich.edu
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: all-bugs at bugzilla.gnome.org


Please describe the problem:
For iradio metadata information gnomevfssrc registers callbacks with gnome-vfs
to send & recieve additional headers.  If gnomevfssrc is NOT in iradio mode, it
still registers this callbacks, which interfere with other applications that may
need to send & recieve additional headers.

I am adding iTunes Music Sharing support to Rhythmbox.  The communcation is done
via HTTP 1.1, and so for getting music files I use an http:// uri passed to a
gstreamer playbin element.  However, I need to send additional headers (a hash
of the file path for authentication purposes) so that iTunes will actually send
the file.  But, since gnomevfssrc /always/ registers the send/recieve callbacks
(and strangely enough it seems gnome-vfs can only have 1 set registered), my
callbacks are never run.  Since this is /definitly/ not iradio mode, the
callbacks do not need to be registered in gnomevfssrc.

I have a patch against gst-plugins 0.8.10, and can remake it against CVS (the
0.8 branch?, so that this can get into Rhythmbox before RB works with 0.9?) if
needed.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.