Does anyone have any links for building RESTful web services with the ASP.NET Web API. So far I have built a very basic web service using WCF and would now like to try the web api to see which one suits for Azure based web services.
I will start from:
ASP.NET Web API: you can find screencasts, getting started info, etc (funny enough it is down at the mo)
And move on to these blogs:
Henrik Nielsen's blog (ASP.NET Web API architect)
Gunnar Piepman's blog
Pedro Reys blog
Tugberk Ugurlu's blog
My own blog
For asking questions, you can try here (SO) and Web API.
FYI, I'm a sucker for a good conference presentation video (RIP MIX...)
This was my introduction to the subject and it gave me a very good crash course on the whys and hows of Web API.
WCF Web APis: "There's a URI for That"
A note of caution: The video is referencing an alpha status of the project so it may include some old terminology. But as Web API is still in beta, I think that point is kind-of moot.
Related
I was reading a couple of articles on how to use Yaws in a RESTful way, how Webmachine maps HTTP semantics to resources and all of them helped a lot to grasp the concept.
Example API in Zack Kessin's Building Web Applications with Erlang
Steve Vinoski's RESTful Services with Erlang and Yaws
Sheehy/Vinoski - Developing RESTful Web Services with Webmachine
This is the point where I got confused: it seems like that Webmachine as a good REST toolkit and Yaws as a mature web server would complement each other instead of writing a REST implementation each time but I had found no trace of these tools being used together. The only relevant google hits were Steve Vinoski's twitter and his github experiment.
I am fairly new to OTP (and Yaws, web development etc) and I might be missing something. Webmachine is a full OTP application, bundled with Mochiweb so my guess would be that it is an overkill but that's just a shot in the dark.
(I know Cowboy has its own REST implementation too but Yaws is more appealing to me and REST is not always a necessity of course.)
In this question, I am told that web API is specifically purposed for making rest services. What are the options for not wanting to follow rest? What are Web API alternatives to REST?
WCF was earlier used to write RESTful services. But, WCF is strongly used towards SOAP based architecture and doesn't fully support (or it is quite difficult to write) the entirety of RESTful architecture.
Hence, WebApi was developed as a lightweight solution to support only RESTful services.
So I'm about to create a mobile application using titanium. I want to use Symfony2 as the server and communicate via rest API's with the client (mobile)
What I am asking is what are the best practices when it comes to designing my server? and what do you recommend I start with?
Have a look at the FOSRestBundle or the Symfony REST Edition, this should get you started quickly.
https://github.com/FriendsOfSymfony/FOSRestBundle
https://github.com/gimler/symfony-rest-edition
As far as RESTful API endpoint design and the data your API will transfer, I really like this guide:
http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api
Granted, this is more of a generic "How do I REST API?" guide, but I think it's useful in a situation like yours.
I am building RESTful web API for my ASP.NET MVC4 web application using ASP.NET WebAPI. I want to use OAuth 1.0 to provide authorization. I'm looking toward of DotNetOpenAuth library. Can anyone help me to understand how to use the service provider of this library with ASP.NET WebAPI?
I'm in a similar situation as you.
I would recommend you to take a look at Thinktecture's IdentityModel Authorization extensions for Web API (and MVC).
It's a open source project hosted on GitHub, with samples to take a look at as well.
You can also grab a lot of useful info from Dominick Baier's blog
Have you looked at the OAuthServiceProvider sample that comes with DotNetOpenAuth? It demonstrates a WCF service that is protected by OAuth 1.0.
I'm an experienced client application developer (C++/C#), but need to come up to speed quickly on writing server side code to perform RESTful interactions. Specifically, I need to learn how to exchange data with OpenSocial containers via the RESTful API.
The RESTWiki is a very good resource and then there is the classic "How I explained REST to my Wife".
However, don't forget to go read about it directly from the source, it is not as difficult a read as it may first seem.
And I am assuming you will be doing REST over HTTP so this will come in very handy.
Lastly, considering OpenSocial supports the Atom Publishing Protocol, this will be useful.
Enjoy.
RESTful Web Services
I found this this to be a good introduction to RESTful web apps, although it doesn't refer to OpenSocial containers.