From: Stefan Kost Date: Fri, 20 Apr 2007 08:21:19 +0000 (+0000) Subject: docs/design/draft-tagreading.txt: Added open issues/thoughts to draft. X-Git-Tag: RELEASE-0_10_13~83 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d5669b316aa7de53146b92ea6ce1650a2a2b3068;p=platform%2Fupstream%2Fgstreamer.git docs/design/draft-tagreading.txt: Added open issues/thoughts to draft. Original commit message from CVS: * docs/design/draft-tagreading.txt: Added open issues/thoughts to draft. --- diff --git a/ChangeLog b/ChangeLog index 1e9be67..b43aa75 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2007-04-20 Stefan Kost + + * docs/design/draft-tagreading.txt: + Added open issues/thoughts to draft. + 2007-04-19 Sebastian Dröge * gst/parse/grammar.tab.pre.c: diff --git a/docs/design/draft-tagreading.txt b/docs/design/draft-tagreading.txt index ac219cc..7f6610f 100644 --- a/docs/design/draft-tagreading.txt +++ b/docs/design/draft-tagreading.txt @@ -36,6 +36,22 @@ The plan is that applications can do the following: * tagread-elements should have RANK_NONE to be not autoplugged by decodebin +Open Issues +----------- +* would it make sense to have 2-phase tag-reading + * 1st phase: get tag-data that are directly embedded in the data + * 2nd phase: get tag-data that has to be generated fetched + * e.g. album-art via web, video-thumbnails +* what about caching backends + * it would be good to allow applications to supply tagbin with a tagcache- + object instance. whenever tagbin gets a uri to tagread, it consults the + cache first. whenever there is a cache-miss it will tag-read and then store + in the cache + + GstTagList *gst_tag_cache_load_tag_data (GstTagCache *self, const gchar *uri); + gst_tag_cache_store_tag_data (GstTagCache *self, const gchar *uri, GstTagList *tags); + + Reuse -----