Issue 81 in musikcube: HTTP streams should use header Content-Range for seeking

[codesite...@google.com]

Status: Accepted
Owner: onnerby
Labels: Type-Enhancement Priority-Medium Component-Server

New issue 81 by onnerby: HTTP streams should use header Content-Range for
seeking
http://code.google.com/p/musikcube/issues/detail?id=81

both the httpstream_plugin and the core::http::TrackSender should use the
http standard "Content-Range" for seeking in filestreams.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #1 on issue 81 by onnerby: HTTP streams should use header

Content-Range for seeking
http://code.google.com/p/musikcube/issues/detail?id=81

This way we can also seek in tracks when playing a from any standard type of
webserver like apache.