Routing in ASP.NET Web API

Comment Posted by martooo

Mon, 20 Feb 2012 10:20:52 GMT

Great stuff! Thanks a lot for the article.

So, what is the best practice to model this:

PurchaseOrder

PurchaseOrderLineItem

One purchase order can have multiple line items. How can I get all the line items under one specific purchase order? How to get a single line item provided that I know the line item id? What will the webapi controller look like?

As above mentioned, action is not recommended, I am really wondering to know how to get it done.

Thanks

Comment Posted by xminder

Fri, 02 Mar 2012 17:44:29 GMT

Great work! Please, how can I do routing like:

GET /user/{userId}/comments

This should get comments posted my a user with specified user id.

Thanks

Comment Posted by patil.pravin31

Tue, 20 Mar 2012 08:51:27 GMT

Awesome article. You have put the contents nicely, so that even a beginner can understand the routing concept. Great job Mike...

Comment Posted by ehdv

Tue, 10 Apr 2012 08:49:40 GMT

Why would a URL like the following be considered an action and therefore not RESTful?

/api/business/{id}/reviews

As best I can tell, this is a noun which can then be gotten, posted to, have a delete or a put applied, etcetera - it's simply a child noun of the parent.

Comment Posted by digitalpacman

Thu, 28 Jun 2012 13:49:37 GMT

Why did you remove UriTemplate()? I feel like that implementation was the best idea. Developers could use that as the connection between clients and code, because the code and client are disconnected systems and they need an easy way to locate the referred action.

Comment Posted by carluman

Thu, 12 Jul 2012 12:22:15 GMT

Thanks, this helped a lot! I knew I was close but this got me the rest of the way.

Comment Posted by pratap reddy

Fri, 13 Jul 2012 06:07:49 GMT

Hi Mike

I am a MVC 3 developer. In real time scenarios, one controller will be dealing with multiple views and View1 may call a method GetAdminUsers() and View2 may call GetCommonUsers().

In this scenario, how we can handle with WEB-API.

I completely understood, using WEB-API, the service calls from JQuery is a big win, but what about application implementation perspective.

Comment Posted by sinedyip

Fri, 13 Jul 2012 14:54:25 GMT

Thank you Mike Wasson nice article

Comment Posted by EricCoffman

Sun, 15 Jul 2012 09:14:06 GMT

I am with pratap reddy, how to use multiple GETs. My get method needs to handle getting a record by Id, by a review period, by status, etc.

Comment Posted by pretzelb

Tue, 17 Jul 2012 13:42:45 GMT

I will echo what a few others are touching on, this seems to indicate that webapi cannot handle what was previously considered RESTful. If you look back in 2008 this MSDN article (msdn.microsoft.com/) had some good information on REST. I'm not sure how you can implement something like this with webapi:

users/{username}/bookmarks?tag={tag}

If you can, then it would be great to update the article.

Comment Posted by tayebi

Mon, 03 Sep 2012 07:36:51 GMT

Thanks Mike, it helps a lot

Comment Posted by yrshaikh

Mon, 08 Oct 2012 01:50:58 GMT

how to handle multiple gets in cases such as this stackoverflow.com/

Comment Posted by amit pachahara

Thu, 06 Dec 2012 08:11:37 GMT

Thanks Mike. This article really clears all my doubts on Web API routing.

Really i am very thankful to you

Comment Posted by itanex

Thu, 07 Feb 2013 16:59:03 GMT

Your ProductsController get method returns an HttpResponseMessage but in appearance should return a ThumbnailImage.

If you return a message object instead of the dataobject that your method is handling does this not break the content negotiation principle of WebAPI?