Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Sidebar 1" sidebar. Defaulting to "sidebar-1". Manually set the id to "sidebar-1" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /usr/share/wordpress/wp-includes/functions.php on line 4139 Tech Notes » throughput

ActiveSync needs a "Back off, dude" Response

performance, throughput No Comments »

Well apparently iOS-6.1, using Microsoft’s ActiveSync, is hurting Microsoft Exchange servers. Yup. Using MS’s API on MS’s servers hurts them. …and it’s Apple’s fault?

See, I don’t get that last part. “Used as defined” and “you’re hurting us!” don’t work together.

For the same reason, I pushed back on a major customer using our Web API to draw metrics from my company’s service. I’m worried over throttling, and resisting the one client turning the user-experience for all other users towards the poor side. We could have introduced the same issue, and I resisted. There’s no throttling or QoS in the Web API.

Maybe if a device using the API is too busy for the service, and “that sucker’s gonna fail”, it just needs a way to say “Back Off”, like Endpoint Congestion Notification on TCP, “BUSY” in SCSI, HTTP/1.1 error code 420 (chill), HTTP/1.1 error code 429 (too many requests), or HTTP/1.1 error code 509 (bandwidth limitation).

… or Exchange needs to know it’s throughput, and advise the clients (ie iOS, or it’s own applications like MS/Outlook) that they have a portion of a limited workload.

Either way, apparently if you have an iOS device running 6.1, you’re a bad man, and it’s your fault that MS/Exchange cannot tolerate MS/ActiveSync load.

WP Theme & Icons by N.Design Studio
Entries RSS Comments RSS Log in