Tuesday, February 26, 2008

Design and Implementation - Episode 3

Update: Part 2 is now available here. I've also updated the links below.


I just got done mixing the first part of the third episode of Design and Implementation, the occasional podcast that Tim and I do. This time, we interviewed John Lam, who is a Product Manager at Microsoft on the DLR team. John has been working on IronRuby, an implementation of the Ruby language on the .NET platform.


Tim has been big into Ruby lately, so we had a good time talking to John. So good, in fact, that we ran fairly long. So I've split the episode in two - the first part is now ready. When I get done mixing the second part, I'll put that up too. Sorry to be a tease. :)


Download episode 3, part 1 (MP3, 30.4 MB).


Previous episodes:


  1. Wow. I had no idea that I'm now in marketing! :)

  2. Should I have called you a Program Manager? It's not my fault MSFT uses those dumbass, confusing titles. :)

  3. Very interesting REST podcasts. You mention the possibility of using ASP.Net MVC for your REST service... at my blog (http://www.shouldersofgiants.co.uk/Blog) I put together a sample that uses ASP.Net MVC to provide a RESTful service along the lines defined by Sam Ruby and Leonard Richardson in their RESTful Web Service book. I chooose MVC over WCF because it had the MVC support and multiple representations built in. The service I ended up with supports XHTML (easy), XML, JSON and a HELP representation. XML required my own XsltResult class. To add "connectedness" to JSON required custom serializers. HELP is a representation that returns the XHTML representation plus some extra documentation and a javascript test harness. I thought this was a good way to allow developers to explore how the service works / reacts more fully than the plain XHTML representation. Skip to entry 16 for a version that works with MVC 1.0. Just going to listen to the dynamic language bits now!