Replying to Avatar jb55

i wouldn’t consider a request-response system like http to be push system just because i temporarily open a connection, make a request, and a response is *pushed* to me.

Push to me is about the initiator of the event.

What if I created a request and got a response? This is not push because i had to “poll” to get the other peer to generate a reaponse.

What if someone generates an event on the network and i am subscribed? Then yes, a user pushed a message to the relay and the relay pushed the message to my device.

The connection is just the thing that enables messages to go back and forth. I don’t think it makes sense to define push/poll based on how the channel was created.
Avatar
Nour 9mo ago

So websockets are push systems now?

The subscriber has to establish a connection with a server and subscribe to a topic.

Reply to this note

Please Login to reply.

Discussion

Avatar
Vitor Pamplona 9mo ago

My point is that they are not because they always require the client to start the connection and "subscribe" to things. They are always pulling.

If the server could start the connection, then it would be a real Push.

Avatar
jb55 9mo ago

they are full duplex channels. its both and neither. you choose the pattern: push, pull, pub/sub, fire‑and‑forget, or a mix.