Topics: Web Api
Dec 5, 2010 at 3:46 PM

Great stuff!

Two questions:

1. Do you plan a processor to handle multipart messages? Previously handling multipart usually required ugly coding in client and server.

2. In the Http query sample, the client knows to deserialize the response from the xml, even though xml was not explicitly defined anywhere. Is it the default? How to use other formats on the client?

Dec 17, 2010 at 8:10 PM


  1. It is not currently high on our priority list. It definitely can be achieved through a custom processor. I will add to our backlog to do a sample on this  in the future. Hopefully the community will step up sooner :-)
  2. WCF Web apis support content negotiation for selecting the formats. The client sends accept headers indicating their preference, and we do a match. For example if you open fiddler with the contact manager sample and send an accept header of "accept: application/json" to the contact/1 resource you will get back json. If you send "accept: application/xml" you get xml. There is a default if no accept headers are sent. In that case it uses xml by default as it takes the first media type registered.