StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
429774
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-01-09T21:17:28.090
FavoriteCount
0
LastActivityDate
2016-04-06T15:08:50.510
LastEditDate
2016-04-06T15:08:50.510
LastEditorUserId
-1
OwnerUserId
53517
ParentId
386973
PostTypeId
2
Score
13
ViewCount
0
LastEditorDisplayName
text
Body
I agree completely that what you want is OAuth; I say that having worked on both OAuth and OpenID systems. I've also been in your boat a few times, having to develop a REST web service api. For a really good ideas on OAuth, and why it is what you want see these attached article: These are must read, there are four parts read them all: <a href="http://hueniverse.com/oauth/guide/" rel="nofollow noreferrer">http://hueniverse.com/oauth/guide/</a> the RFC, read after reading above as it can be a little daunting for most: <a href="http://oauth.net/core/1.0" rel="nofollow noreferrer">http://oauth.net/core/1.0</a> And then finally maybe some code. I have a couple projects hosted that are using Java/Groovy to do OAuth. One is a plain old OAuth client, the other is a client for specific interactions with NetFlix. <a href="http://www.blueleftistconstructor.com/projects/" rel="nofollow noreferrer">http://www.blueleftistconstructor.com/projects/</a> If you are relatively inexperienced with REST (you haven't built a full scale web api yet) I would recommend that you buy (or better get your boss to) "RESTful Web Services" by Richardson & Ruby. It is an O'Reilly book. I can say that it is one of their better books to debut in the past few years. It might also help to look at some RESTful OAuth based APIs. The NetFlix API is a perfect example: <a href="http://developer.netflix.com/docs" rel="nofollow noreferrer">http://developer.netflix.com/docs</a> Good luck and happy coding!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWeb Service Authentication using OpenID
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USRob Ottaway
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWeb Service Authentication using OpenID
 singulars
 PostTypePostTypeId
 PTQuestion
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. 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.