On Sep 9, 2012 12:17 PM, "Justin Karneges" <jus...@affinix.com> wrote: > > You're correct in that it is reliable under the hood. The problem is really > just that most TCP APIs don't expose to the app what has been acknowledged. It > is pretty sad that everyone solves this by layering acks on top, when acks are > already being performed a layer down.
Thank you guys for explaining this, I finally get it. Too bad the application layer doesn't have access to that information.... probably breaks some random OSI rules and causes problems in some use cases I'm just not thinking about (or maybe not?). > > I think it would be neat if QAbstractSocket had another signal, like > bytesAcknowledged(), that worked by using platform-specific methods to figure > out what has been definitely sent. That sounds good too, but what I meant was more of a generic ack layer for the [Qt] applications to use (you said lots of people end up having to do it). d3fault
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
