Communication Rate Adjustment Extension

1. A system for handling an adjustment request of a WebSocket communication rate, comprising: a communication interface configured to receive a WebSocket frame; and a processor configured to: determine that the WebSocket frame includes a new desired WebSocket communication rate, wherein the new desired WebSocket communication rate was provided by a sender of the WebSocket frame, a recipient of the new desired WebSocket communication rate is not obligated to adjust the WebSocket communicate rate of the recipient to the new desired WebSocket communication rate, a payload data portion of the WebSocket frame includes a control byte sequence and a control message that indicates the new desired WebSocket communication rate, the control byte sequence is not included in a header of the WebSocket frame, and the control byte sequence included in the payload data portion identifies that the control message is included in the payload data portion, and a code is included in the header of the WebSocket frame, and the code identifies that the WebSocket payload data portion is eligible to include the control byte sequence and the control message but the inclusion of the code in the header of the WebSocket frame does not require the WebSocket payload data portion to include the control byte sequence and the control message in the WebSocket payload data portion, and a capability to utilize the control byte sequence was negotiated between the sender and the recipient during initialization of a WebSocket connection of the WebSocket frame including by receiving an extended capability request, assigning the control byte sequence in response to the request and providing the assigned control byte sequence for use by the sender; and adjust a transmission rate of a WebSocket communication based at least in part on the received new desired WebSocket communication rate.

2. The system of claim 1 , wherein the WebSocket frame was sent by the sender when the sender detected that a receive rate at which WebSocket frames are being received is not optimal.

3. The system of claim 2 , wherein it was determined that the receive rate is not optimal at least in part by detecting that the receive rate is faster than a processing rate of the WebSocket frames.

4. The system of claim 2 , wherein it was determined that the receive rate is not optimal at least in part by detecting that one or more processing resources of the sender have reached a specified utilization level.

5. The system of claim 1 , wherein the new desired WebSocket communication rate was determined by the sender of the WebSocket frame at least in part by detecting a device power state.

6. The system of claim 1 , wherein the new desired WebSocket communication rate was determined by the sender of the WebSocket frame at least in part by detecting a processor power state of the sender.

7. The system of claim 1 , wherein the new desired WebSocket communication rate was determined by the sender of the WebSocket frame at least in part by detecting a battery state of the sender.

8. The system of claim 7 , wherein the battery state includes one or more of the following: a battery power level, a type of a battery, and a charging state of the battery.

9. The system of claim 1 , wherein the new desired WebSocket communication rate was determined by the sender of the WebSocket frame at least in part by analyzing a power utilization history.

10. The system of claim 1 , wherein the new desired WebSocket communication rate was determined by the sender of the WebSocket frame at least in part by detecting a type of communication link being utilized by the sender.

11. The system of claim 1 , wherein the new desired WebSocket communication rate was determined by the sender of the WebSocket frame at least in part by detecting an amount of allocated bandwidth consumed.

12. The system of claim 1 , wherein the new desired WebSocket communication rate includes a byte per second rate.

13. The system of claim 1 , wherein the new desired WebSocket communication rate includes a relative rate change director indicator.

14. The system of claim 1 , wherein adjusting the transmission rate includes adjusting a quality of a data being communicated.

15. The system of claim 1 , wherein adjusting the transmission rate includes adjusting a sampling of a data being communicated.

16. The system of claim 1 , wherein adjusting the transmission rate includes reducing the transmission rate.

17. The system of claim 1 , wherein adjusting the transmission rate includes restoring a default transmission rate.

18. The system of claim 1 , wherein the new desired WebSocket communication rate is associated with a processing rate of the sender of the WebSocket frame.

19. The system of claim 1 , wherein the new desired WebSocket communication rate was determined based at least in part on an amount of received but unprocessed data of the sender of the WebSocket frame.

20. The system of claim 1 , wherein the indicator of the new desired WebSocket communication rate includes an acknowledgement message that a sender has processed a received data.

21. The system of claim 1 , wherein the processor is further configured to determine the new desired WebSocket communication rate at least in part by using information included in the WebSocket frame.

22. The system of claim 1 , wherein the new desired WebSocket communication rate is limited by an assigned rate limit associated with the WebSocket communication.

23. A system for requesting an adjustment of a WebSocket communication rate, comprising: a processor configured to: detect that a rate at which WebSocket data are being received is not optimal; and determine a new desired WebSocket communication rate; and a communication interface configured to notify a WebSocket communication sender of the new desired WebSocket communication rate, wherein the WebSocket communication sender that received the new desired WebSocket communication rate is not obligated to adjust the WebSocket communicate rate of the WebSocket communication sender to the new desired WebSocket communication rate, to notify the WebSocket communication sender of the new desired WebSocket communication rate includes at least using a payload data portion of a WebSocket frame that includes a control byte sequence and a control message that indicates the new desired WebSocket communication rate, and the control byte sequence is not included in a header of the WebSocket frame, and the control byte sequence included in the payload data portion identifies that the control message is included in the payload data portion, and a code is included in the header of the WebSocket frame, and the code identifies that the WebSocket payload data portion is eligible to include the control byte sequence and the control message but the inclusion of the code in the header of the WebSocket frame does not require the WebSocket payload data portion to include the control byte sequence and the control message in the WebSocket payload data portion, and a capability to utilize the control byte sequence was negotiated between the WebSocket communication sender and the system during initialization of a WebSocket connection of the WebSocket frame including by sending an extended capability request and receiving the control byte sequence that was assigned in response to the request.

24. The system of claim 23 , wherein the new desired WebSocket communication rate was determined based at least in part on an amount unprocessed data of the system.

25. A method for handling an adjustment request of a WebSocket communication rate, comprising: receiving a WebSocket frame; using a processor to determine that the WebSocket frame includes a new desired WebSocket communication rate, wherein the new desired WebSocket communication rate was provided by a sender of the WebSocket frame, a recipient of the new desired WebSocket communication rate is not obligated to adjust the WebSocket communicate rate of the recipient to the new desired WebSocket communication rate, a payload data portion of the WebSocket frame includes a control byte sequence and a control message that indicates the new desired WebSocket communication rate, the control byte sequence is not included in a header of the WebSocket frame, and the control byte sequence included in the payload data portion identifies that the control message is included in the payload data portion, and a code is included in the header of the WebSocket frame, and the code identifies that the WebSocket payload data portion is eligible to include the control byte sequence and the control message but the inclusion of the code in the header of the WebSocket frame does not require the WebSocket payload data portion to include the control byte sequence and the control message in the WebSocket payload data portion, and a capability to utilize the control byte sequence was negotiated between the sender and the recipient during initialization of a WebSocket connection of the WebSocket frame including by receiving an extended capability request, assigning the control byte sequence in response to the request and providing the assigned control byte sequence for use by the sender; and adjusting a transmission rate of a WebSocket communication based at least in part on the received new desired WebSocket communication rate.

26. A computer program product for handling an adjustment request of a WebSocket communication rate, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for: receiving a WebSocket frame; determining that the WebSocket frame includes a new desired WebSocket communication rate, wherein the new desired WebSocket communication rate was provided by a sender of the WebSocket frame, a recipient of the new desired WebSocket communication rate is not obligated to adjust the WebSocket communicate rate of the recipient to the new desired WebSocket communication rate, a payload data portion of the WebSocket frame includes a control byte sequence and a control message that indicates the new desired WebSocket communication rate, the control byte sequence is not included in a header of the WebSocket frame, and the control byte sequence included in the payload data portion identifies that the control message is included in the payload data portion, and a code is included in the header of the WebSocket frame, and the code identifies that the WebSocket payload data portion is eligible to include the control byte sequence and the control message but the inclusion of the code in the header of the WebSocket frame does not require the WebSocket payload data portion to include the control byte sequence and the control message in the WebSocket payload data portion, and a capability to utilize the control byte sequence was negotiated between the sender and the recipient during initialization of a WebSocket connection of the WebSocket frame including by receiving an extended capability request, assigning the control byte sequence in response to the request and providing the assigned control byte sequence for use by the sender; and adjusting a transmission rate of a WebSocket communication based at least in part on the received new desired WebSocket communication rate.