Explain API Controllers.

 API Controllers

  • API Controller is just a normal Controller, that allows data in the model to be retrieved or modified, and then delivered it to the client. It does this without having to use the actions provided by the regular controllers.
  • The data delivery is done by following a pattern known by name as REST. REST Stands for REpresentational State Transfer pattern, which contains 2 things:
a) Action Methods which do specific operations and then deliver some data to the client. These methods are decorated with attributes that make them be invoked only by HTTP requests. 

b) URLs that define operational tasks. These operations can be sending full or part of data, adding, deleting, or updating records. In fact, it can be anything.


  • MVC and API controllers both derive from the Controller class, which derives from ControllerBase:

public class MyMvc20Controller Controller {} [Route("api/ [controller]")]

public class MyApi20Controller Controller {}

  • As of Core 2.1 (and 2.2), the template-generated classes look a little. different, where a Web controller is a child of the Controller class and an
  • API controller is a child of ControllerBase.

public class MyMvc21Controller: Controller {}

[Route("api/[controller]")]

public class MyApi21Controller : ControllerBase {}


This can be expressed in the table below:



Comments

Popular posts from this blog

Short note on E-Government Architecture

Discuss classification or taxonomy of virtualization at different levels.

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?