空歡喜
篤vs督
- 讓大尾篤成為一則典故 Quote: 一個再富地方色彩,再有詩意或形
Traditional sockets implementations have an irritating limitation, atleast for TCP sockets: it is impossible to gracefully and cleanly shutdown listening (server) sockets.The problem is that kernels accept new TCP connections for listeningsockets without asking your server; accept() doesn't actually accept the connection, it just gives you the next one that the kernel hasalready accepted on your behalf.
This means that to shut down cleanly,you need a two-stage process: first you tell the kernel to stop acceptingnew connections
早前跟友人談到一些語文和討論的問題,在此整理一下自己的想法。當然,我不是語文專家,只是純粹思考訓練而已,也可能說得不對。
毫無疑問地,語文是人類最重要的工具之一。通過語文,我們可以將抽象的想法,簡化成文
Using Unix domain sockets from Python's socket module is prettyeasy, but underdocumented. Since I've done it (and I may want to doit again sometime):
AF_UNIX .I usually go whole-hog and explicitly specify SOCK_STREAM as well. .bind() and .connect() is the path ofthe Unix socket file. For .bind() , the file can't already exist
Real cat-5 wiring, such as what they run through the walls of buildings,has eight wires; 100 Mbps and 10 Mbps Ethernet use four wires. If youhave fixed cat-5 runs that you can't afford to add to, and you reallyneed additional ports in places that already have one, and you can'tafford to buy switches, you can take advantage of this to double uptwo Ethernet ports onto a single cat-5 run.
That's an Ethernet