[gstreamer-bugs] [Bug 571604] registry feature are replaced during first use

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=571604

  GStreamer | gstreamer (core) | Ver: git

Jan Schmidt changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thaytan at mad.scientist.com




------- Comment #3 from Jan Schmidt  2009-02-14 10:32 UTC -------
Please look at my branch in http://cgit.freedesktop.org/~thaytan/gstreamer/ -
I've made a lot of changes to the way the registry handles stuff.

It preserves this piece of functionality though, because:
a) At the moment, the registry doesn't know whether someone has a reference to
the feature (from a registry lookup). If someone else is using the
PluginFeature, we can't go replacing it.
b) More importantly, the plugin details that were loaded from the registry
cache might not match the details from the actual plugin file when we go to
load it (it *might* have been replaced between the initial scan and the load
request). Hence, even if we checked that the only reference was the one the
registry has, we couldn't ensure it was up to date without replacing each entry
of the feature details anyway.

Nevertheless, making this stuff faster is the next thing I want to do, after
merging my WIP registry-rewrite branch... 


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=571604.