Geek Answers Handbook

What are the REST API options for the .NET 3.5 stack

I am currently on the .Net 3.5 stack (including VS2008 tools) and will not be updated anytime soon. What options are available to me for creating an unreliable API that will be used by my own web application. I see my options as:

  • MVC2 (less choice, as the team is not comfortable)
  • WCF with HTTP toolkit. (I don’t know which version I should look for for my stack)

I need the following functions:

  • Cookie authentication (I really like the ActionCilter approach for MVC for this)
  • Resource-based authorization (User, account, etc. Again, I like the AF approach to this)
  • Everything works under HTTPS

My uncertainty about which versions, etc. I browse for my stack, and what are the arguments for and against each?

+4
source share
2 answers

There are several options:

I found several others on the Internet, but I know nothing about:

You can use MVC directly, but keep in mind that this is not designed as a REST infrastructure, so you do not think how to harmonize the content for you. You would have to build it yourself. Depending on what you are trying to do, this can be a lot of work, or it can be quite simple.

+3
source

Also see Mindtouch Dream : it is a very mature server and a leisure client server. Some points

  • It has very good support for asynchronous services.
  • can work with .net 3.5 or mono.
  • the latest version can also be integrated with Asp Mvc (optional, its final independence from asp).
  • him on github

(I'm not sure if it will satisfy your authentication / authorization needs)

+1
source

More articles:


All Articles