Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Seems to me like you need two ASP.NET MVC projects; one for the REST interface, and one for the Web UI. But at the end of the day it's just more controller methods. Commented Jul 28, 2016 at 21:18
  • @RobertHarvey apologies that I didn't mention that it's PHP based(edited my question now), but that should not make much difference. Commented Jul 29, 2016 at 7:55
  • 1
    As you probably don't want to change the behaviour of the existing WebUI too much, I would advise to use separate controllers (responding of different URI endpoints) for the WebUI and the REST API. Those controllers would share the service and data layers. Commented Jul 29, 2016 at 10:25
  • 1
    @Abbakkar I think you are confusing terminology some what here. "REST" is the web, HTTP is a REST protocol. REST is an architectural design that the web conforms to, including webpages read by browsers. I think you might be confusing REST with something like a JSON API instead of HTML webpages (understandable, people keep making that mistake). Commented Jul 29, 2016 at 13:33
  • I noticed that you put a bounty on this. What sort of authoritative or credible source did you have in mind? How will the authoritative nature of that source help you write your application? Commented Aug 3, 2016 at 20:06