StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6753768
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-19T20:34:44.760
FavoriteCount
0
LastActivityDate
2011-07-19T20:34:44.760
LastEditDate
LastEditorUserId
0
OwnerUserId
503320
ParentId
6719051
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<p>The fact that you're using a web server shouldn't change much about your model. You're still building chat. You also don't want to make your chats tied too deeply to the process that is managing their HTTP connection. HTTP connections are ephemeral, even if everything is going well and you're using long polling there's no guarantee that the connection will be re-used with Keep-Alive for the next long poll. The user might also want to open up the same chat in multiple browser windows, multiple computers, whatever.</p> <p>I haven't looked closely at any of these but you're not the first person that has built web chat with Erlang:</p> <ul> <li><a href="http://chrismoos.com/2009/09/28/building-an-erlang-chat-server-with-comet-part-1/" rel="nofollow">http://chrismoos.com/2009/09/28/building-an-erlang-chat-server-with-comet-part-1/</a></li> <li><a href="http://www.erlang-factory.com/upload/presentations/31/EugeneLetuchy-ErlangatFacebook.pdf" rel="nofollow">http://www.erlang-factory.com/upload/presentations/31/EugeneLetuchy-ErlangatFacebook.pdf</a></li> <li><a href="http://yoan.dosimple.ch/blog/2008/05/15/" rel="nofollow">http://yoan.dosimple.ch/blog/2008/05/15/</a></li> <li><a href="https://github.com/yrashk/socket.io-erlang" rel="nofollow">https://github.com/yrashk/socket.io-erlang</a> (more of a general tool for this sort of thing, not chat specifically)</li> <li><a href="https://github.com/rvirding/chat_demo" rel="nofollow">https://github.com/rvirding/chat_demo</a> (as seen above)</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POErlang web-distribution
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USYOUR ARGUMENT IS VALID
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
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.