Why is it a no-go?


On Sun, Oct 27, 2013 at 4:04 PM, arnova <notifications@github.com> wrote:

> In xbmc/filesystem/File.cpp:
>
> >
> >      if (m_flags & READ_CACHED)
> >      {
> >        // for internet stream, if it contains multiple stream, file cache need handle it specially.
> > -      m_pFile = new CFileCache((m_flags & READ_MULTI_STREAM)!=0 && isInternetStream);
> > +      m_pFile = new CFileCache((m_flags & READ_MULTI_STREAM) != 0 && URIUtils::IsInternetStream(url, true));
>
> Ok, but we at least need some way to turn off buffering completely.
> Currently https (or anything else using tls/ssl + curl) + buffering is a
> no-go on RPi and we need some way to work around that. In the future we
> could simply add options to as.xml to handle this on a per-protocol basis,
> as suggested. Agreed?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/xbmc/xbmc/pull/3429/files#r7236816>
> .
>