On 07.10.2006, at 00:51, Stephen Deasey wrote:
Something else we can try is a Linux and BSD socket option which
causes a listening socket to only generate a readable event when a new
socket arrives *and* there is data to read. Usually, you get one when
a new connection arrives, you accept(),
On 10/7/06, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
On 07.10.2006, at 00:51, Stephen Deasey wrote:
Something else we can try is a Linux and BSD socket option which
causes a listening socket to only generate a readable event when a new
socket arrives *and* there is data to read. Usually,
Stephen,
i checked your patch for AS 4.1 regarding acceptmax, we can adopt it
for our driver as well
No, nothing bad. I think it's a great idea!
But some of the newer APIs for this are weird because they handle more
than socket IO, and we are worried about portability, right? I'm just
We can. It's not that big of a change.
I was just generally holding off on adding new things to the driver
because there's a lot of code in there now and it's getting hard to
manage.
On 10/7/06, Vlad Seryakov [EMAIL PROTECTED] wrote:
Stephen,
i checked your patch for AS 4.1 regarding
On 9/25/06, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
Unix is not Unix as I see...
Please note this (interesting) document:
http://developers.sun.com/solaris/articles/event_completion.html
Mostly interesting, as there is now a very powerful and scalable
notification interface on both
On 06.10.2006, at 23:41, Stephen Deasey wrote:
What's the goal? We can certainly abstract socket event IO, with
poll() as a fallback. But some of the interfaces you mentioned here
can handle waiting on other things, e.g. signals. Is this what you
want?
At the moment only as replacement
On 10/6/06, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
On 06.10.2006, at 23:41, Stephen Deasey wrote:
What's the goal? We can certainly abstract socket event IO, with
poll() as a fallback. But some of the interfaces you mentioned here
can handle waiting on other things, e.g. signals. Is
Unix is not Unix as I see...
Please note this (interesting) document:
http://developers.sun.com/solaris/articles/event_completion.html
Mostly interesting, as there is now a very powerful and scalable
notification interface on both Solaris and Mac OSX (aka BSD)
Unixes. Windows has it as well,
We use Linux only, so it will not affect us but if using new API will
change the way the program works, how it will be possible to support
Solaris, Linux, Windows and MaxOSX at the same time?
Zoran Vasiljevic wrote:
Unix is not Unix as I see...
Please note this (interesting) document:
On 25.09.2006, at 21:42, Vlad Seryakov wrote:
We use Linux only, so it will not affect us but if using new API will
change the way the program works, how it will be possible to support
Solaris, Linux, Windows and MaxOSX at the same time?
The same way as it is possible to maintain Windows
On 9/25/06, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
Unix is not Unix as I see...
Please note this (interesting) document:
http://developers.sun.com/solaris/articles/event_completion.html
Mostly interesting, as there is now a very powerful and scalable
notification interface on both
11 matches
Mail list logo
