sockets - why the cookies continues working -


i have question reason web applications continues setting cookies, because persistent http conections use sockets, i.e.: websocket.

http 1.1 , 2 uses persistent http conections, sockets in client , server. these sockets active necessary time loading complete web page (html, css, images, etc), sockets killed server. logic due server not know doing client. so, in scenario, use of cookies justified.

but, websocket think scenary different, because uses 1 socket, means after conection done, server , client uses sockets sending data.

so, question is... why cookies necessary if server know client?

this question impossibly broad, since many different web applications work in many different ways.

in general, cookies used store data needs persist beyond momentary connection between client , server.

more specifically, connection between client , server can transient. server receives request, sends page, , moves on next request. doesn't maintain constant connection every browser contacts it.


Comments

Popular posts from this blog

java - UnknownEntityTypeException: Unable to locate persister (Hibernate 5.0) -

python - ValueError: empty vocabulary; perhaps the documents only contain stop words -

ubuntu - collect2: fatal error: ld terminated with signal 9 [Killed] -