Barry,
FYI, I didn't just throw out an idea and pull some code out of my ass.
I have tackled this exact issue for a client that needed to stop a
stream from downloading when they closed the stream, and couldn't
actually kill streams when the user interaction resulted in spamming new
NetStreams. The solution is to throttle the requests, using the exact
code I provided.
If you're saying you call
ns.pause();
ns.close();
ns = null;
and the NetStream continues to download afterwards *when you do not
attempt to open another NetStream*, then there's something else going on
because that works. If you immediately try to play another stream, even
if it's not on same NetStream instance, then the previous one will not
stop downloading (that's the bug).
When you throttle the requests for new streams, the problem goes away.
-Steven
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
