http://tcllib.sourceforge.net/doc/comm.html
Background: comm is a communication package. It essentially reimplements the send command known from Tk in terms of sockets. The original author is John Robert LoVerso.
Can one use comm as an exact replacement for send? Apparently not - using send, an interpreter registers itself and other Tk applications can query this registry to find out what interpreters are available. If you are just using comm, this is not the case.
EE: Well then, how does an application using comm find out who it can talk to?
AK: There is a little nameserver application at http://www.purl.org/net/akupries/soft/pool/pkg_Pool_Net.html Application have to explicitly register. In that way comm is not as automatic as tk's send.
Category Package, subset Tcllib