StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWebSockets versus Long-Polling versus TCP Scalability/Ease of Use
primarykey
Id
3365219
data
AcceptedAnswerId
3373749
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-07-29T17:12:27.147
FavoriteCount
0
LastActivityDate
2017-10-17T14:39:30.647
LastEditDate
2017-10-17T14:39:30.647
LastEditorUserId
1000551
OwnerUserId
398371
ParentId
0
PostTypeId
1
Score
4
ViewCount
3404
LastEditorDisplayName
text
Body
<p>I'm writing a backend for a mobile web-app based in Java and I was wondering as far as scalability and ease of use go what are the pros and cons associated with using WebSockets versus Long-Polling solutions like comet. Another option would also be implementing my own solution using TCP. From what I've read it seems that you need to run Long-polling solutions on dedicated servers as they don't run well in Tomcat/Jetty when you start dealing with large numbers of users. WebSockets sounds like it scales better. Are there any disadvantages to going with Websockets over Comet or should I just resort to my own solution using TCP connections? I'm looking for the option that uses the least traffic.</p>
Tags
<java><websocket><long-polling>
Title
WebSockets versus Long-Polling versus TCP Scalability/Ease of Use
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USVadim Kotov
UserOwnerUserId
1. USuser398371
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. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POWebSockets versus Long-Polling versus TCP Scalability/Ease of Use
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  POWebSockets versus Long-Polling versus TCP Scalability/Ease of Use
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
3. VO
  singulars
  PostPostId
  POWebSockets versus Long-Polling versus TCP Scalability/Ease of Use
  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.