StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18250112
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-15T09:42:48.027
FavoriteCount
0
LastActivityDate
2015-11-04T09:34:26.307
LastEditDate
2015-11-04T09:34:26.307
LastEditorUserId
665507
OwnerUserId
665507
ParentId
18249847
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
As long as you can write a specification for the data you send through the TCP socket, you've got your own protocol. It's mostly about defining commands and payloads. You've got to serialize your command packet before putting them through TCP. Endianness is a common pitfall if you pack the packet in binary format. XML and JSON are common text-based data exchange formats. Personally I'm pro-JSON. Do refer to <a href="http://bsonspec.org/" rel="nofollow noreferrer">BSON</a>, <a href="https://msgpack.org/" rel="nofollow noreferrer">MessagePack</a> or <a href="https://github.com/google/protobuf" rel="nofollow noreferrer">protobuf</a> for binary serialization. They pack the typed data into binary so they have better type checking than text based serialization and more compact in size. They also handle endian conversion, packet versioning and provide drivers/bindings in various languages. The server and client could have been written in different languages. EDIT: added RFC samples Seeing the comment by Ross Patterson, I also recommend reading RFC for protocol definition references. <a href="http://tools.ietf.org/html/rfc2326" rel="nofollow noreferrer">RTSP</a> and <a href="http://tools.ietf.org/html/rfc2616" rel="nofollow noreferrer">HTTP</a> are text protocols, <a href="http://tools.ietf.org/html/rfc3550" rel="nofollow noreferrer">RTP</a> and media formats (<a href="http://tools.ietf.org/html/rfc3640" rel="nofollow noreferrer">MPEG4 AV</a>, <a href="http://tools.ietf.org/html/rfc6184" rel="nofollow noreferrer">H-264</a>) are binary protocols. EDIT: <a href="http://www.infoq.com/interviews/protocol-serialization-todd-montgomery" rel="nofollow noreferrer">Demystifying Protocols and Serialization Performance with Todd Montgomery</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to build a protocol on top of tcp?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USleesei
UserOwnerUserId
1. USleesei
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to build a protocol on top of tcp?
 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
 VTUpMod
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.