StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POConceptualizing RESTful API endpoints as views in the MVC design pattern
primarykey
Id
6045791
data
AcceptedAnswerId
6063928
AnswerCount
1
ClosedDate
2017-02-09T23:28:59.523
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-18T13:48:14.850
FavoriteCount
5
LastActivityDate
2011-05-19T19:34:22.100
LastEditDate
2011-05-18T13:54:07.327
LastEditorUserId
184045
OwnerUserId
184045
ParentId
0
PostTypeId
1
Score
4
ViewCount
911
LastEditorDisplayName
text
Body
As I am trying to describe a system I built in a research paper, I came across the following notational problem when trying to represent the complexity of the system I created: <ul> <li>Assume I engineer service A, communicating with the world solely through its RESTful endpoints. Then, I engineer service B, that uses service A as its backbone and represents its data to the external world.</li> <li>Assume that service A has its own models and data controllers. Should then the RESTful endpoints be conceptualized as views in the MVC pattern?</li> <li>Assume that service B has its own set of proxy models that map more or less directly models of service A. It provides a set of GUI views to the users, with a completely separate set of controllers. Where does service A come in the MVC? Should it be represented as an encapsulated model?</li> </ul> Real world example (not related to the problem I am working on) would be: <ul> <li>del.icio.us and pinboard.in provide roughly akin set of APIs, and thus can be swapped as a service A for service clients (for the purposes of question assume they are both built upon MVC pattern, but may have completely different sets of models and controllers)</li> <li>Delibar is an iOS app, and thus follows the MVC schema and matches requirements for service B; assume Delibar models its data after the data models of service A as represented in the API endpoints.</li> </ul> Are thus pinboard.in and del.icio.us the model for Delibar? Are RESTful endpoints the views? And are thus the view sets for pinboard.in and del.icio.us the same?
Tags
<model-view-controller><api><design-patterns><rest>
Title
Conceptualizing RESTful API endpoints as views in the MVC design pattern
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USbogo
UserOwnerUserId
1. USbogo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.