> With any system implementing ACK packets (tcp is one example) a link that fails but is then fixed is the same as a very slow link. This is only even theoreti

> With any system implementing ACK packets (tcp is one example) a link that fails but is then fixed is the same as a very slow link. This is only even theoretically true if a) you have no bound on memory and b) the link will always come back up. In practice, neither of these is true. Further, if you're relying on never being partitioned then any network break requires delaying availability until the partition is resolved. CAP is then relevant if you're not willing to do this (and virtually no one is going to be so inclined).