They've been flogging WebAPI in recent MSDN magazines, but I got the impression that it's just REST more formalised with contracts.
Perhaps this makes sense from the hints I've been reading. WCF is heavy and complicated and over-engineered to be general purpose (which is fine and I've benefited from that). REST is consumable by everyone, but it's a typeless mess. Putting some structure over REST and giving it a name sounds like a typical progression. Oh well, I'd better start converting my brand new code to yet another standard. You can't have too many standards I reckon. Greg
