Re: Multithread safety
- From: "Mike Gleason Jr Couturier" <abuse@xxxxxxxxxxxx>
- Date: Sun, 6 Nov 2005 10:02:17 -0500
>
> I am not sure what exactly you mean by full-duplex in this context so I'll
> assume that you want to read and write simultaneously rather than in
> request-response fashion. In this case you need to break the BSD barrier
> and use asynchronous I/O offered by Winsock. Unless you need full Unix
> compatibility (and even then) it rarely makes sense to limit yourself to
> BSD-style sockets only. They were invented in a different world with
> different performance characteristics and application architectures than
> the one you develop for.
>
I understand! Would you advise me provide an interface similar
to CAsynchSocket in my library? Do you have any readings on the
subject?
I want to create myself a library usable both in console apps and
GUI apps. The idea of creating an hidden window to receive network
events sounds overkill to me.. but if its the way to go! Plus, it seems
that calls to reading and writing to the socket are a little serialized..
Another question: If someone is sending me a 1mb file, will I receive
hundreds of FD_READ message, even if I'm continuously reading
the socket?
I would need a good article on Winsock specific functions I guess :)
But you showed me the way to go, I'm on a start!
Mike
.
- Follow-Ups:
- Re: Multithread safety
- From: Eugene Gershnik
- Re: Multithread safety
- From: Mike Gleason Jr Couturier
- Re: Multithread safety
- References:
- Multithread safety
- From: Mike Gleason Jr Couturier
- Re: Multithread safety
- From: Eugene Gershnik
- Re: Multithread safety
- From: Arkady Frenkel
- Re: Multithread safety
- From: Mike Gleason Jr Couturier
- Re: Multithread safety
- From: Eugene Gershnik
- Re: Multithread safety
- From: Mike Gleason Jr Couturier
- Re: Multithread safety
- From: Mike Gleason Jr Couturier
- Re: Multithread safety
- From: Eugene Gershnik
- Multithread safety
- Prev by Date: Re: How do I trap winsock calls in the runtime...
- Next by Date: Re: Multithread safety
- Previous by thread: Re: Multithread safety
- Next by thread: Re: Multithread safety
- Index(es):
Relevant Pages
|