When to use TCP and HTTP in node.js?

Question

Stupid question, but just making sure here:

When should I use TCP over HTTP? Are there any examples where one is better than the other?

ZZ Coder · Accepted Answer · 2010-04-28 22:31:18Z

10

TCP is full-duplex 2-way communication. HTTP uses request/response model. Let's see if you are writing a chat or messaging application. TCP will work much better because you can notify the client immediately. While with HTTP, you have to do some tricks like long-polling.

However, TCP is just byte stream. You have to find another protocol over it to define your messages. You can use Google's ProtoBuffer for that.

answered Apr 28, 2010 at 22:31

ZZ Coder

75.7k30 gold badges139 silver badges170 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

M Nottingham · Accepted Answer · 2010-04-30 23:23:00Z

1

Use HTTP if you need the services it provides -- e.g., message framing, caching, redirection, content metadata, partial responses, content negotiation -- as well as a large number of well-understood tools, implementations, documentation, etc.

Use TCP if you can't work within those constraints. However, if you use TCP you'll be creating a new application protocol, which has a number of pitfalls.

answered Apr 30, 2010 at 23:23

M Nottingham

5,8841 gold badge27 silver badges23 bronze badges

Collectives™ on Stack Overflow

When to use TCP and HTTP in node.js?

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related