I am currently working on a Flash socket client for a pre-existing service/standard. The service uses TCP flow control to throttle itself and the Flash socket is reading in everything as fast as it can despite not being able to process it as fast as it’s being taken in. This causes the bytesAvailable on the socket to keep increasing and the server never knows that the client has fallen behind.
In short, is there any way to limit the size of bytesAvailable for a Flash Socket object or throttle it in some other way?
Note: Rewriting the server isn’t a viable option at the current time as it’s a standard and the client’s utility drops immensely if server-side changes are needed
After research I’ve found that the Actionscript Socket class will start throttling when CPU is maxed out on the system (likely due to running out of resources/slow response times).
This has actually solved my problem as I’ve written the code such that it strikes a balance between how many frames per second the app “wants” and how many bytesAvailable are in the socket. If bytesAvailable is too high the app will process non-stop and drive CPU to 100%, ultimately causing the socket to slow down.