Jakob Eriksson wrote:
Jan Zerebecki wrote:
On Fri, Sep 22, 2006 at 12:04:40PM +0100, Robert Shearman wrote:
I appreciate your attempt at solving this hard problem, but I don't
believe this is the right approach. Using winsock2 instead of Unix
sockets adds overhead in terms of wineserver call
Damjan Jovanovic wrote:
On 9/22/06, Robert Shearman <[EMAIL PROTECTED]> wrote:
Using WSAEVENTs is an interesting approach, but I'd rather see Unix
sockets being used with a thread that select's on the socket and sets a
Win32 event instead. Also, I think this amount of nesting is confusing
and co
Jan Zerebecki wrote:
On Fri, Sep 22, 2006 at 12:04:40PM +0100, Robert Shearman wrote:
I appreciate your attempt at solving this hard problem, but I don't
believe this is the right approach. Using winsock2 instead of Unix
sockets adds overhead in terms of wineserver calls and extra processing
On Fri, Sep 22, 2006 at 12:04:40PM +0100, Robert Shearman wrote:
> Damjan Jovanovic wrote:
> >Changelog:
> >* Makes RPCRT4 use Winsock2 instead of native sockets (needed for
> >event object support)
> >* Adds support for TCP (ncacn_ip_tcp protocol) servers
>
> I appreciate your attempt at solving
Damjan Jovanovic wrote:
Changelog:
* Makes RPCRT4 use Winsock2 instead of native sockets (needed for
event object support)
* Adds support for TCP (ncacn_ip_tcp protocol) servers
I appreciate your attempt at solving this hard problem, but I don't
believe this is the right approach. Using winsoc
