Re: APC/socket fix (final?)

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Claudio Natoli" <claudio(dot)natoli(at)memetrics(dot)com>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: APC/socket fix (final?)
Date: 2004-03-26 19:29:27
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34B5F6@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

>> The third option is to redefine all these functions into our own, and
>> implement our own emulation layer. This means our own
>select(), send(),
>> recv() (more? I don't think so). And have these call the
>native winsock
>> APIs (WSAEventSelect(), WSASend(), WSARecv() etc). These
>functions are
>> designed to work in an APC environment.
>
>Pardon me for not having paid close enough attention, but what versions
>of select() and friends are we relying on now? Is it really reasonable
>to think that we can do a better job without a large amount of effort?

oh yeah, I should add that these "new-style" functions are very similar
to the original functions in syntax and semantics - they're just changed
to interface with the win32 style of blocking/signalling/waiting.

//Magnus

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-03-26 19:39:41 Re: APC/socket fix (final?)
Previous Message Tom Lane 2004-03-26 19:11:27 Re: APC/socket fix (final?)