| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.

View
 

WCF Web APIs

Page history last edited by Glenn Block 9 years, 6 months ago

WCF Web API

Programatically expose application functionality / services over HTTP to a large range of clients. Build RESTful services which leverage the intermediaries of the web and which are inherently evolvable.

 

Links:

 

Clarifications 

There were a few things I said in the session about HTTP that well, just weren't true. Below are the clarifications. Yes, even blue badges make mistakes. :-)

  1. I said: Location header can be set to a relative URI. False. RFC2616 clearly says that location header must be absolute. I have updated the sample / test code to show you how can generate an absolute by using the request URI which you can get off of HttpRequestMessage<T>.
  2. I said: POST should always return a status 201 or 202 and not a 200. False. POST should only return a 201/202 IF it is creating a resource. Henrik rightly pointed out that in most cases when POST is used there is no resource created. For example a person may POST an order for a pizza and only get back a receipt without a resource being created for the order.

 

 

RIA/JS 

Create data driven jQuery applications with ease.

 

Links

 

 

 

 

 

 



Comments (0)

You don't have permission to comment on this page.