When you say processing is done on the client side, would that include compute-intensive tasks such as applying filters, gesture recognition, H.264 encoding/decoding, image de-noising, etc.?
Additionally, you mentioned that "they set up the client to use TCP, HTTPS, and HTTP as a fallback for consistent user experience".
When you say processing is done on the client side, would that include compute-intensive tasks such as applying filters, gesture recognition, H.264 encoding/decoding, image de-noising, etc.?
Additionally, you mentioned that "they set up the client to use TCP, HTTPS, and HTTP as a fallback for consistent user experience".
-What use cases or scenarios would have TCP be the fallback for UDP to maintain consistent user experience?
Great, succinct article by the way! Just how I love it--start simple, then dive into the details thru progressive discovery.
When you say processing is done on the client side, would that include compute-intensive tasks such as applying filters, gesture recognition, H.264 encoding/decoding, image de-noising, etc.?
Additionally, you mentioned that "they set up the client to use TCP, HTTPS, and HTTP as a fallback for consistent user experience".
-What use cases or scenarios would have TCP be the fallback for UDP to maintain consistent user experience?
Great, succinct article by the way! Just how I love it--start simple, then dive into the details thru progressive discovery.