Why is websockets called as HTTP-push based technology

Question

0.00/5 (No votes)

See more:

Since Websockets work over TCP and not HTTP, why do we still call it HTTP-push based technology. Apologies if it's a silly question. I am new to client-server architecture.

What I have tried:

why do we still call it HTTP-push based technology

Posted 13-May-21 9:13am

Zeke Anderson

Updated 13-May-21 9:58am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

raddevus · Answer 1 · 2021-05-13T09:58:00

Because push-based means you don't have to poll anything.
In the case of websockets you set up the socket and then it is event-based -- when something changes on the server then the client is automatically "pushed" the changes.
In previous technologies you'd have to set up a client timer (or something like that) and then when the timer fired, you'd have to poll the server to see if there was a change. If there was a change then you'd do something.

With websockets this polling becomes unnecessary because instead the changes at the server are "pushed" to all subscribed clients.