4 ms·
> I don't understand his emphasis on session on TCP and UDP. A session requires nothing more than a "unique" number to identify it. ... which requires three ro
by exDM69 11y ago
> I don't understand his emphasis on session on TCP and UDP. A session requires nothing more than a "unique" number to identify it.
... which requires three round trip times for the client and server to agree upon.
UDP gives the flexibility of sending "payload" starting from packet #1. There may be session identifiers in that package, too.
- ww520 11y agoHe didn't talk about performance at all. If he said TCP is slower than UDP, fine, that's a perfectly valid reason to use UDP. But he was talking about TCP imposes the notion of session on the application while UDP doesn't, which are false. If he meant the TCP connection as a session, why he led the discussion to managing session with locks and threads in application. Then he talked of the ease of Erlang handling session while other languages having a hard time, which was an exaggeration. Session management is a solved problem, in many languages by many people.