On Mon, Aug 8, 2016 at 11:20 AM, Tom Hacohen <t...@osg.samsung.com> wrote: > Why do we need a "sent" event? Shouldn't this just be handled by whoever > is calling "send" and then check error code or whatever?
That send is asyncrhonous, it will queue and monitor fd for write, when select/poll reports that, then it will try to write and report back. Alternatively if we move read to just be notification, then it would make sense to make write the same, then it will issue a simple write() and no extra infra around that (thus will change to return ssize_t and set errno, which can be EAGAIN if socket is non-blocking, or less than requested amount if not all data can be written). This would move some logic from the core to outside, making developer's lives bit harder since they will have to handle memory management for partial writes on their own. -- Gustavo Sverzut Barbieri -------------------------------------- Mobile: +55 (16) 99354-9890 ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
