websocket - What is the difference between web sockets, long polling, server-sent events and forever frame? -
i'm exploring signalr, technology supports transports (web wockets, long polling ,server-sent events , forever frame).
i have understood terminology web sockets , long polling. server-sent events , forever frame?
how 4 differ each other?
transports , fallbacks of signalr:
websocket full-duplex
websocket full-duplex communication channels on single tcp connection. when both server , browser support, only transport establishes true persistent, two-way connection between client , server.
server sent events simplex
also known eventsource technology browser receives automatic updates server via http connection. server-sent events eventsource api standardized part of html5 w3c.
forever frame one request -> 1 infinite response
forever frame creates hidden iframe makes request endpoint on server that not complete. server continually sends script client executed, providing one-way realtime connection server client. connection client server uses separate connection server client connection, , standard http request, new connection created each piece of data needs sent.
ajax long polling (one request -> 1 response [but delayed]) repeated
long polling not create persistent connection, instead polls server request stays open until server responds, @ point connection closes, , new connection requested immediately. may introduce latency while connection resets.
more info:
https://docs.microsoft.com/en-us/aspnet/signalr/overview/getting-started/introduction-to-signalr https://en.wikipedia.org/wiki/server-sent_events
Comments
Post a Comment