WCF and MySpace: a RESTful MIX session!

Myspace » WCF and MySpace: a RESTful MIX session!

Myspace » WCF and MySpace: a RESTful MIX session! — Fri, 01 Feb 2008 03:27:28 GMT

PingBack from http://myspace.freedombloghost.info/?p=24496

MySpace presenting at MIX on RESTful WCF

Fri, 01 Feb 2008 06:14:19 GMT

Most people consider Windows Communication Foundation ( WCF ) as a great framework for communicating

MySpace at MIX 08

VolkerW's WebLog — Fri, 01 Feb 2008 06:16:41 GMT

We all knew MIX is cool. But I guess these folks are always good for One more. Vittorio just announced

MySpace at MIX 08

Noticias externas — Fri, 01 Feb 2008 06:49:48 GMT

We all knew MIX is cool. But I guess these folks are always good for One more. Vittorio just announced

MySpace presenting at MIX on RESTful WCF

Noticias externas — Fri, 01 Feb 2008 06:49:52 GMT

Most people consider Windows Communication Foundation ( WCF ) as a great framework for communicating

MySpace does WCF

The Cybertopian Chronicle — Fri, 01 Feb 2008 07:12:37 GMT

My friend Vittorio has posted that MySpace will be talking about WCF at Mix 2008 ( see it here ). This

MySpace does WCF

Noticias externas — Fri, 01 Feb 2008 07:51:23 GMT

My friend Vittorio has posted that MySpace will be talking about WCF at Mix 2008 ( see it here ). This

MySpace at MIX 08

News — Fri, 01 Feb 2008 09:37:41 GMT

We all knew MIX is cool. But I guess these folks are always good for One more. Vittorio just announced

re: WCF and MySpace: a RESTful MIX session!

Chris Ortman — Sun, 03 Feb 2008 05:18:46 GMT

I hope I can make it to mix this year if only to see this session.

I experimented with using WCF to do a restful API a while back but ultimately abandoned it because I thought it would be better built using an MVC framework (take your pick Rails, MonoRail, System.Web.MVC) than WCF.

I'll be interested to know what advantages WCF can provide over the MVC route.

re: WCF and MySpace: a RESTful MIX session!

Steve Maine — Wed, 06 Feb 2008 09:21:08 GMT

Chris, that's a great question. It makes we want to turn it around and ask what advantages the MVC factoring has over the WCF factoring given equivalent functionality.

The way I see it, there are two world views rapidly trending towards the same middle ground. On one side, we have the services folks who have been builing components/services for a long time. These guys are long-tailing towards reach protocols like plain HTTP because it makes their services accessable to more clients. On the other side, we have the web folks who have been building content-driven presentation layers for a long time and are now realizing that returning structured data in addition to HTML/images/CSS/script can be quite interesting.

As a result, you have a situation where depending on what world view they're affinitized to, one group of people will look at a problem and see services and another group will look *at the exact same problem* and see web pages. And they will both be right, from a certain point of view.

An interesting pivot here is how the state model for the UI differs (or does not differ) from the state model of the "service". For stateless services that primarily respond to HTTP GETs (i.e. idempotent data retrieval operations), the choice is largely aesthetic. If you view these things as just another type of content your website returns, you're likely to be happier using something like MVC. If you view these things as idempotent services that your application exposes, then you can use WCF.

A major selling point of WCF is that it lets people who have already adopted a "services" mindset use a single programming model to build those services, regardless of the underlying protocol details. MVC has a different pitch; it lets people who are used to building content-driven sites stretch those techniques beyond simple HTML into the structured data world. These two technologies will inevitably meet in the middle.

It gets interesting when you move beyond idempotent operations and into the world of state management. MVC frameworks are really tuned for the stateless case. Services (particularly workflow services) are good at managing long-running user state that lives beyond a particular browser session. In those cases you can either front your services with an MVC controller, or expose your services to the outside world directly.

http://gazitt.com/blog/

TrackBack — Thu, 07 Feb 2008 18:52:27 GMT

http://rhizohm.net/irhetoric/

TrackBack — Fri, 08 Feb 2008 00:41:34 GMT

MIX08: what happens in Vegas...

Vibro.NET — Thu, 28 Feb 2008 11:12:05 GMT

Next week I am going to MIX ! If you are there as well and you want to take the chance to sync up on

MIX08: what happens in Vegas...

Noticias externas — Thu, 28 Feb 2008 12:09:02 GMT

Next week I am going to MIX ! If you are there as well and you want to take the chance to sync up on

WCF & REST at MIX08: The Tale of MySpace APIs

Vibro.NET — Thu, 06 Mar 2008 23:56:47 GMT

Yesterday we finally had the session about the making of MySpace APIs . As you'll be able to see from

WCF & REST at MIX08: The Tale of MySpace APIs

Noticias externas — Fri, 07 Mar 2008 00:17:17 GMT

Yesterday we finally had the session about the making of MySpace APIs . As you'll be able to see