September 13, 2005
@ 03:35 PM

In planning for our future releases, I came up against a design question that I'd like to see solved in future versions of the .NET Framework. The basic scenario is a website that wants to expose a web service using a number of different protocols (SOAP, XML-RPC, JSON, Plain Old XML (POX), etc) without having to write a lot of duplicate code. For example, the Flickr web services expose 3 interfaces for each method (SOAP, XML-RPC and POX).

From my perspective, this is something that should be handled by a protocol agnostic web services stack which is what the Windows Communications Foundation (aka Indigo) is supposed to be. On the other hand, the ASP.NET team's recently announced Atlas project is targetted server-side AJAX development.

What I want to know is basically this, if I want to create web services that utilize both SOAP & JSON does that mean I have to adopt both Indigo and Atlas?

Can some helpful soul at PDC ask this at any sessions on Indigo or Atlas? I guess I can always wait until next week and get the info from the horses mouth but product teams tend to give better answers to external customers than us internal MSFT folks. :)


Thursday, September 15, 2005 10:16:09 PM (GMT Daylight Time, UTC+01:00)

If you saw the Lap that Chris, Scott, Anders and I did, we simply used a JSON binding for our plain-old-Indigo service that we later used with POX, REST, SOAP, and Infocard with no changes to the code.

And yes, we should have lunch. I need to convince you that there's a year six that makes sense :-)

Comments are closed.