StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20021095
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-16T16:53:40.870
FavoriteCount
0
LastActivityDate
2013-11-16T17:42:22.607
LastEditDate
2013-11-16T17:42:22.607
LastEditorUserId
80586
OwnerUserId
80586
ParentId
10958063
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I think the correct way to do this is to implement content negotiation into your application. Yeah, Express 3.x facility is a way to do it and provides a direct answer to your question, but I don't think it's the best way to do it because it places the content negotiation responsibility in the routing logic. I don't think that's a good place for it because it doesn't follow the <a href="http://en.wikipedia.org/wiki/Single_responsibility_principle" rel="nofollow">single responsibility</a> principle, having put the content negotiation in routing logic. I've taken a stab at implementing content negotiation in my <a href="https://github.com/ijoey/joeyguerra/blob/master/represent.js" rel="nofollow">blog engine</a>; reviewing that might help guide you in a good direction. The gist is that the code determines the file extension via content negotiation logic. Then, with the file extension, it wants to find the corresponding view file, renders it into a response and sends it back to the client. The idea is that it responds with the requested resource in the requested representation per the content negotiation. The <a href="https://github.com/ijoey/joeyguerra/blob/master/resources/index.js#L23" rel="nofollow">routing logic</a> only specifies a view, but has no idea about content negotiation. That happens outside of the routing logic which makes for a more flexible design. The result of this design is the ability to ask for a specific representation of the resource like: <a href="http://blog.joeyguerra.com/index.json" rel="nofollow">http://blog.joeyguerra.com/index.json</a> and get a JSON representation <a href="http://blog.joeyguerra.com/index.phtml" rel="nofollow">http://blog.joeyguerra.com/index.phtml</a> and get partial (or an HTML fragment) HTML representation <a href="http://blog.joeyguerra.com/index.xml" rel="nofollow">http://blog.joeyguerra.com/index.xml</a> and get an XML representation.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSet up REST routes in Express JS for Ajax only to use with Backbone
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJoey Guerra
UserOwnerUserId
1. USJoey Guerra
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. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.