There was an update to
in the last few days. I haven't had a chance to check if it has fixed any of this, but I suspect that it has not (I did update the NuGet packages and pushed the change to CodePlex, but I've only done a quick smoke test).
From poking around, it appears that the cache brain damage is a fundamental problem with the device's HTTP stack. WP8.1 and Windows 8.1 add XHR_PROP_NO_CACHE to
that lets one turn if off.
As for the out-of-memory problem, I've built a Windows Runtime Component that wraps the
C++ REST SDK
. I can play streams with it, but the code in http_win8.cpp has the same brain damage as HttpClient. It keeps allocating buffer blocks without bound as data arrives (fixable in the available
C++) and it uses the same broken cache IXMLHTTPRequest2 implementation (again, apparently not fixed until WP8.1). There does not seem to be a simple way to fix the out-of-memory problem without either duplicating a good chunk of the C++ REST SDK code or by
forking the project.
I haven't quite decided how to proceed. A C# or C++ HTTP implementation running directly on top of a network socket would be necessary to really fix things. The one positive right now, is that phonesm's web code is pluggable and can be customized without ripping
into code spread all over the project.
And this is nearly two decades after the