Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
How not to get a protocol implementation merged
Posted Jan 20, 2011 10:22 UTC (Thu) by renox (subscriber, #23785)
I wonder why they did it this way?
Me I would have authorised the initiation of the connection (INIT) with a data filed with the possibility of the server (INIT ACK) replying that it dropped the data (either to simplify its implementation or because it is overloaded in case a cracker try to spoof IPs) thus requiring the client to re-send the data.
With this simple design, you have low-latency(*) and security..
*: only if the server isn't overloaded though.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds