StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13374764
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-11-14T07:44:28.333
FavoriteCount
0
LastActivityDate
2012-11-14T07:53:17.453
LastEditDate
2012-11-14T07:53:17.453
LastEditorUserId
1289384
OwnerUserId
1289384
ParentId
8187860
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You can't return a reference of any kind via JSON-RPC. There is no standard to do so (afaik) because RPC is stateless, and most developers prefer it that way. This simplicity is what makes JSON-RPC so desirable to client-side developers over SOAP (and other messes). You could however adopt a convention in your return values that some JSON constructs should be treated as "cues" to manufacture remote "object" proxies. For example, you could create a modified JSON de-serialiser that turns: <pre><code>{ "__remote_object": { "class": "Some.Remote.Class", "remote_id": 54625143, "smd": "http://domain/path/to/further.smd", "init_with": { ... Initial state of object ... } } } </code></pre> Into a remote object proxy by: <ul> <li>creating a local object with a prototype named after <code>class</code>, initialised via <code>init_with</code></li> <li>downloading & processing the <code>smd</code> URL</li> <li>creating a local proxy method (in the object proxy) for each procedure exposed via the API, such that they pass the <code>remote_id</code> to the server with each call (so that the server knows which remote object proxy maps to which server-side object.)</li> </ul> While this scheme would be workable, there are plenty of moving parts, and the code is much larger and more complicated on the client-side than for normal JSON-RPC. JSON-RPC itself is not well standardised, so most extensions (even SMD) are merely conventions around method-names and payloads.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POjsonrpc2 returning remote reference
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDavid-SkyMesh
UserOwnerUserId
1. USDavid-SkyMesh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POjsonrpc2 returning remote reference
 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
 VTAcceptedByOriginator
CommentsPostId
1. COThats a good way to solve it yes. By now my project is stateles and that keeps the code nicer. But this is a nice way to 'hint' at remote references. (sorry for the late response)
 singulars
 PostPostId
 PO
 UserUserId
 USBram

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.