Oh, I guess I don't know very much about how it works
then -- Does NetLibSocketAccept block even if you set
the socket to be non-blocking?
--- [EMAIL PROTECTED] wrote:
> According to the documentation:
> Accepts the next connection request from a remote
> client. This call is
> only applicable to stream-based sockets. Before
> calling NetLibSocketAccept
> on a socket, a server application needs to:
> Open the socket (NetLibSocketOpen()).
> Bind the socket to a local address
> (NetLibSocketBind()).
> Set the maximum pending connection-request queue
> length (
> NetLibSocketListen()).
> NetLibSocketAccept will block until a successful
> connection request is
> obtained from a remote client. After a successful
> connection is made, this
> call returns with the address of the remote host in
> *sockAddrP and the
> socket descriptor of a new socket as the return
> value. You then use the
> new socket to send and receive data.
>
> If you're doing all that and in the same order then
> I would look to your
> client?
>
>
> /**************************************************
> Heath Schaefer
> Product Engineer
> Sporlan Division, Parker Hannifin Corporation
> 636.239.7711 x243
> **************************************************/
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
