Home > Archive > Unix Programming > March 2007 > linux async sockets
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
linux async sockets
|
|
| John Doe 2007-03-24, 10:07 pm |
| How portable are they? Cygwin, BSD?
| |
| Frank Cusack 2007-03-25, 7:04 pm |
| On Sun, 25 Mar 2007 01:33:03 +0100 John Doe <NOTOSPAMjohndoe64738@yahoo.com> wrote:
> How portable are they? Cygwin, BSD?
WHAT are they?
| |
| Logan Shaw 2007-03-25, 7:04 pm |
| Frank Cusack wrote:
> On Sun, 25 Mar 2007 01:33:03 +0100 John Doe <NOTOSPAMjohndoe64738@yahoo.com> wrote:
>
> WHAT are they?
I'm guessing they're this:
http://aem.sourceforge.net/aemip.html
What I can't figure out is why, according to this documentation, there doesn't
seem to be any support for writing to a socket. Sure, you can write in
response to a read, but sooner or later, you're going to write more than
the kernel can buffer and your write() will block, or even with non-blocking
mode, you're going to make no progress and have to guess when to try again.
It would be nice to have an event that says "now would be a good time to try
writing again". Of course, maybe I'm missing something and there's a
programming technique that makes this unnecessary.
As for portability, I'm guessing this is extermely UNportable. It doesn't
even seem to run on stock versions of Linux; you have to add some extra
kernel support.
- Logan
| |
| John Doe 2007-03-25, 7:04 pm |
| How about signal-driven sockets with O_ASYNC flag set?
|
|
|
|
|