[Bug 774830] uri: Add new uri API to get URI fragment as table

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=774830

--- Comment #7 from Seungha Yang <sh.yang at lge.com> ---
(In reply to Tim-Philipp Müller from comment #6)
> Isn't returning a hash table going to be awkward for bindings?

Can I get some more information about "be awkward for bindings", please?

If your intention was concerning for a kind of case that 
"what happen if non-Media Fragment URI but just URI Fragment was parsed and
converted to hash table?", my answer is that unexpected "key-value" pair will
be returned. 

For example, "http://foo/var/file#&&=afragment" will be converted to
key = "" (null string) and value = "afragment".

This API cannot guarantee the "validity" of returned "key-value" pair (such as
null key value case), but just do split of URI fragment string based on "&" and
"=". For unknown extended standard that might be somewhere, It is doubtful
whether it should be validated.
As an expanded usecase what I know for [&, = driven "key-pair" rule] is
MPEGDASH. It's defining "period" and "as" as a keys but which are undefined
keys by Media Fragments URI 1.0.

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