18 Jan
2013
18 Jan
'13
2:56 p.m.
Hi, I'm looking through PEP 3156 and the Tulip code, and either something is missing or I'm not looking in the right places. I can't find any sort of callback / future return for asynchronous writes, e.g. in transport. Should there be no "data_sent" parallel to "data_received" somewhere? Or, alternatively, "write" returning some sort of future that can be checked later for status? For connections that aren't infinitely fast it's useful to know when the data was actually sent/written, or alternatively if an error has occurred. This is also important for when writing would actually block because of full buffers. boost::asio has such a handler for async_write. Eli