On (Tue) May 04 2010 [09:43:04], Gerd Hoffmann wrote:
> On 05/04/10 09:17, Amit Shah wrote:
>> Add a non-blocking write handler that can return with -EAGAIN to the
>> caller and also callback when the socket becomes writable.
>>
>> Non-blocking writes are only enabled for sockets that are opened in
On 05/04/10 09:56, Amit Shah wrote:
The logic will be pretty much the same for all filehandle-based backends
on unix. So maybe create some helper functions, so implementing
$backend_chr_write_unblocked can be done with just three lines of code?
Yes, that's the next step. Let's push this for no
On 05/04/10 09:17, Amit Shah wrote:
Add a non-blocking write handler that can return with -EAGAIN to the
caller and also callback when the socket becomes writable.
Non-blocking writes are only enabled for sockets that are opened in
non-blocking mode and only for callers that have registered a ca