Re: Multithread safety

That is of course true. Scalability at least is unimportant for
clients, however, whereas portability might be important.
While I agree the code won't be 100% platform independent,
it's much easier to port code based on puire BSD APIs than
one based on the extended WinSock functions and concepts.
Then again, portability is not important for a lot of folks anyway...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

"Eugene Gershnik" <gershnik@xxxxxxxxxxx> wrote in message
news:eHzLsHI5FHA.2036@xxxxxxxxxxxxxxxxxxxxxxx
> Alexander Nickolov wrote:
>> BSD Sockets happily support multiple socket I/O on a single
>> thread. The trick is to use non-blocking sockets and select
>> judiciously.
>
> Sure, but this approach doesn't scale well and is not very Windows
> friendly (you cannot wait for I/O and other Windows kernel objects
> simultaneously and such).
>
>
> --
> Eugene
> http://www.gershnik.com
>
>


.

Relevant Pages

  • Re: Multithread safety
    ... > BSD Sockets happily support multiple socket I/O on a single ... The trick is to use non-blocking sockets and select ...
    (microsoft.public.win32.programmer.networks)
  • Re: Someone explain (Mc)Clim to me as if I were 5 years old
    ... stream, true callbacks, access to the many Tk/Tcl libs, and terrific ... portability (of more than just the native look/feel GUI -- sockets, ...
    (comp.lang.lisp)
  • Re: Multithread safety
    ... up to 64 simultaneous sockets present no problem in the ... BSD model since a single thread can handle them for I/O. ... At some point the number of threads in the client ... whereas portability might be important. ...
    (microsoft.public.win32.programmer.networks)