I am creating
REST API application and stuck on the part where I should consume the REST service.
I am not sure how to find the way let me accomplish the following:
1. I don't want it to be
Pure REST in another meaning I don't want to lose the ability to use
2. I want to have Simple and efficient Consuming for
API without redundancy
In way help me to get
proxy classes in Client without forcing problem in having duplicate Model in client Side.
What I reach So far (And correct me if I wrong)
1. I Can use
WCF which Achieves me the second approach Using
DataContract but it doesn't look the same for the first approach which will require me to create the
Session with my own.
2. Or Going with
Web API 2 to get leverage from having
session built in,
There is a way to Achieves me the second approach Using
OData wich would help me in generating proxy classes.
Did someone had the same issue? Can you give any pros/cons of each system? And what is the best Simple and Elegant way to go with?
To be more precisely
Currently, I have a .NET platform that I need to expose to different clients
(ASP.NET MVC, iOS and Android), I will be developing these clients myself not a third party.
In the meantime, those Clients have their own business layer which executes some logic and persists data using
entity framework ODTC into an
what I am thinking now and what I need is to have the
ASP.NET Web API 2 or
To serve those clients
by migration the business layer and unified it into API
which one should I use ?
what is the best efficient approach to accomplish the past two scenarios ?
Thanks in advance