william_os4y (william_os4y) wrote,
william_os4y
william_os4y

Non blocking connections

By testing my Fapws3 webserver on different type of systems, I've discovered a strange behaviour of the Linux kernels.

Indeed on Linux, despite my dfferent tests, I've never had the "EAGAIN" error. On the opposite, on OpenBSD 4.6 I receive a lot of those errors during the write process.

OpenBSD is reporting that this error pop's-up because the resource is not available. Within a non-blocking context this sounds logic. Indeed, the resource can still be busy with the previous write when we try to send the new one.

Now the valid question is why we don't have such behaviour on the linux kernel ?

I must deeper investigate, but if someone has a explanation, I'm interested.


William
http://github.com/william-os4y/


ps:
I've used OpenBSD-4.6
Linux-2.6.31 from Archlinux and Ubuntu
Subscribe

  • Bux fixe in Fapws3

    First of all Fapws3 is not dead :-). I read some people saying that the project is no more updated and thus, should be dead. This is not true !!!…

  • Fapws3-11 is out

    Despite what said in February, I decide to release a new version of Fapws3 for Python-2.x. Indeed, thanks to several testors (Blacknoir, Wigunawan)…

  • Fapws3-0.10 is out

    Despite lot of progress on the python3 branch, I propose a new release of Fapws3 for python2.x. Indeed, since 1 year (date of the last stable…

Comments for this post were disabled by the author

  • Bux fixe in Fapws3

    First of all Fapws3 is not dead :-). I read some people saying that the project is no more updated and thus, should be dead. This is not true !!!…

  • Fapws3-11 is out

    Despite what said in February, I decide to release a new version of Fapws3 for Python-2.x. Indeed, thanks to several testors (Blacknoir, Wigunawan)…

  • Fapws3-0.10 is out

    Despite lot of progress on the python3 branch, I propose a new release of Fapws3 for python2.x. Indeed, since 1 year (date of the last stable…