One of the last things I did before leaving the MSDN team was to prototype a Web service for retrieving content programmatically. It’s been a while since then, but a production version is now live . Craig provides an excellent introduction here . The prototype client we always talked about was msdnman - a command line tool like the Unix man command. Craig was the lucky one - he got to build it . It will be interesting to see what people do with these services. Off the top of my head, I can imagine including actual docs in a technology site, integrating with tools (a la’ Reflector), and building a team level doc repository on TFS that allows you to annotate, add your own docs, etc. Anyway, congrats to the MTPS team for a job well done!
Content suppressed by ://URLFAN, for full article visit source
Two articles, one good and one bad...From: pluralsight.com
Post Date: 2006-05-19 07:30:00
I ran into two Web service related articles recently. One really resonated with me: Enable the Service Oriented Enterprise , in the MS Architecture Journal. It presents the Enterprise Service Orientation Maturity Model, or ESOMM. Okay, I know what you’re thinking: eeeeeeeewwww, a maturity model! But it’s a lot more interesting and useful than you think (and they distance themselves from that other MM in a sidebar). Lots of developers and some architects think abou...
more MSDN Content Web Services online...From: pluralsight.com
Post Date: 2006-06-12 05:58:00
One of the last things I did before leaving the MSDN team was to prototype a Web service for retrieving content programmatically. It’s been a while since then, but a production version is now live . Craig provides an excellent introduction here . The prototype client we always talked about was msdnman - a command line tool like the Unix man command. Craig was the lucky one - he got to build it . It will be interesting to see what people do with these services. Off the top of my head,...
more Three reasons that REST is not RPCFrom: pluralsight.com
Post Date: 2007-04-28 12:01:00
I’ve gotten several comments saying that, at the end of the day, REST is just RPC. That’s wrong, for at least 3 very reasons:
1) Each unique state in your protocol state machine has its own URI. That’s different from an RPC endpoint that maintains a black-boxed state machine at a single endpoint. Being able to do state transition processing at disparate locations is hugely powerful. Watch the URLs you are navigating through as you browse, shop and checkout at Amazo...
more 
Websites mentioned in article
Buzz Words mentioned in article:
How popular is www.pluralsight.com?
