Twitter is dropping XML. They recently announced that by March 5th, 2013 their API will no longer support XML as a data format - API v1.1 will support JSON only. What’s the big deal?
It means that every app powered by the Twitter API with XML will break.
Despite the growing popularity of JSON, many developers prefer XML. They are familiar with the parsing libraries, the schema and a powerful collection of XML tools. But after Twitter drops XML, apps built on the XML API will start to see HTTP error responses instead of XML responses. Something like:...
Last week I wrote that if you're API doesn't support JSON and JSONP - you're doing it wrong. I don't think that's terribly controversial.
But is JSON (and JSONP) perfect for everything you need to support with your API? Is XML dead?
Daniel Jacobson of NPR posted a fascinating piece about how NPR tackles a common problem – what’s the best way to render content on a variety of devices, from modern web browsers with top-notch CSS implementations that look almost like typesetting (like Safari) to mobile phones using WAP to low-end devices like HD Radio receivers that don’t understand anything but plain ASCII text.
NPR’s clever solution is to strip markup out of the text and store it in a database table, indexed by position in the text document. To re-generate the content for a particular device, their software queries...
The cost of IT security breaches has almost doubled from 2008 according to this piece via ComputerWorld Canada.
While we'd love to tell you this is just a problem for our Canadian friends - unfortunately we all need to understand API attack types.
(Remember in our Cloud security tech talks last week we saw that for breaches over a certain size you may even need to issue a press release!)
Here are 10 threats that we cover in our API threat protection policy pack.
1. Malicious Code Injection: exploits backend...