Garrett Rooney wrote: > On 4/5/06, Matti Eskelinen <[EMAIL PROTECTED]> wrote: > > > As far as I know there is no way to make the pollset code not use > AcceptEx, so you'd have to implement such a thing yourself inside the > pollset code. > > As for the potential bug, it would probably be easier for a > windows-savy developer to help you out if you actually posted the code > you're having trouble with. > > -garrett > > The problem with AcceptEx is usually because of poorly written Windows winsock 2 Layered Service Providers (LSP's)
I found this app which may help: http://www.cexx.org/lspfix.htm At one point in my life I had to write an LSP an haven't fully recovered at just how backwards and difficult the WS2 architecture forced the LSP's design to be. Back then (on NT4 pre SP6), even a fully compliant LSP would cause system boot failure because many required RPC based services would fail because of the ability of LSP's to make file handles that are unusable with select() and friends. At that time, I believe you were not allowed to call select on a bunch of handles if those handles were created/managed by different LSP's. I don't know if that has changed since then. More information about the absurd brain dead design (IMHO) of LSP's are at: http://www.microsoft.com/msj/0599/LayeredService/LayeredService.aspx Microsoft has a nifty tool which will show you all the LSP's in your system, and give you the option of re-ordering them. If AcceptEx() fails on numerous LSP's, then there should be an option in apr to work around it. Of course the best solution would be to get LSP's that are fixed but that is problematic. LSP's are used for encrypted tunnels and content filtering, etc. Regards, Jeff
