[Bug 778592] souphttpsrc: Add sessions/caching to souphttpsrc

[GStreamer (GNOME Bugzilla)]

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

--- Comment #4 from Stephan Hesse <tchakabam at gmail.com> ---
(In reply to Sebastian Dröge (slomo) from comment #3)
> Sounds like a good plan or at least useful in general. 

Nice that you agree, let me know if you have any more ideas in this direction!

> Cache invalidation is a bit tricky in the general case though.

Hm I kind off know what you mean, but not sure. Can you give an example?

Probably these things should really be left to decide by the application. We
shouldn't look into the actual protocol or app payload specifics I think.
Either its enabled and it checks if the URI is "mapped" on the filesystem at
the chosen path and push it (leaving the actual protocol implementing URI
handler inactive), or we are disabled and just pass on all the calls to the
actual URI handler which may get the data.

What do you think? I am probably missing something, right? :) What would be
your approach?

> 
> Do you plan on working on this, Stephan?

Would be a nice little thing to do, but just for fun ;) Can't guarantee this
will be production-ready anytime soon. But I d be happy to churn out a basic
version of it.

@Sean-Der What do you mean by "this can be solved by the application"?

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