Tech Notes

After a failed attempt to use a Dream Cheeky OIC to discipline a dog’s affection for a sofa, I see that the AC13 roving tank is upgraded. http://www.openipcam.com/forum/index.php?topic=261.0 shows a teardown of the older AC13, http://techbloginator.wordpress.com/2013/02/09/spytank-teardown/ has a more recent teardown but seems unaware of the previous.

The real question is whether I could get away with purchasing this newer variant in an attempt to begin milling a proper embedded OS for it (rather than the serial fire-and-forget what’s-inittab-for crap most often seen)

Projects. Hmm. Need a workshop first…

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.