StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2395724
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-03-07T09:14:05.293
FavoriteCount
0
LastActivityDate
2010-03-07T09:14:05.293
LastEditDate
LastEditorUserId
0
OwnerUserId
182748
ParentId
2395703
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I think you need to work directly with byte arrays returned by the socket functions. For these purposes it's good to have two distinct parts of a message in your protocol. The first part is a fixed-size "header". This will include the size of the byes that follow, the "payload", or, <code>data</code> in your example. So, to borrow some of your snippets and expand on them, maybe you'll have something like this: <blockquote><pre> typedef struct { unsigned int sender_id; unsigned int sequence_number; unsigned int data_length; // this is new } PacketHeader;</pre></blockquote> So then when you get a buffer in, you'll treat it as a <code>PacketHeader*</code>, and check <code>data_length</code> to know how much bytes will appear in the byte vector that follows. I would also add a few points... <ul> <li>Making these fields <code>unsigned int</code> is not wise. The standards for C and C++ don't specify how big <code>int</code> is, and you want something that will be predictable on all compilers. I suggest the C99 type <code>uint32_t</code> defined in <code><stdint.h></code></li> <li>Note that when you get bytes from the socket... It is in no way guaranteed to be the same size as what the other end wrote to <code>send()</code> or <code>write()</code>. You might get incomplete messages ("packets" in your terminology), or you might get multiple ones in a single <code>read()</code> or <code>recv()</code> call. It's your responsibility to buffer these if they are short of a single request, or loop through them if you get multiple requests in the same pass.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POVariable sized packet structs with vectors
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USasveikau
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. COThanks for the advice!
 singulars
 PostPostId
 PO
 UserUserId
 USRev316

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.