Yes. You cannot serialize sockets. So you need a persistent program on your server that keeps the socket open. That persistent program gives the client ("web browser") a token ("a session id", "a cookie") that associates the socket with the client. When some client connects again to your server process and presents the appropriate token, you know which connection to reuse.
In reply to Re^5: Creating Socket Connections that are persistent across multiple page loads in a single web session
by Corion
in thread Creating Socket Connections that are persistent across multiple page loads in a single web session
by unlinker
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |