From: Ted Dennison <dennison@telepath.com>
Subject: Re: Sockets in Apex
Date: 2000/02/09
Date: 2000-02-09T00:00:00+00:00 [thread overview]
Message-ID: <87sgpl$rr9$1@nnrp1.deja.com> (raw)
In-Reply-To: 87s92v$lke$1@nnrp1.deja.com
In article <87s92v$lke$1@nnrp1.deja.com>,
reason67@my-deja.com wrote:
> When I connect a non-blocking client socket in a task in the threaded
> model, errno does not seem to be set by the underlying C. When I run
> in the non-threaded model, or I connect the client without any tasks
> (just the main), or I make the socket block, everything works fine.
I don't have access to your system docs, but I'd bet the answer's in
there. Typically threaded C libraries update a per-thread version of
errno, rather than the global errno. The reason for doing it this way
should be obvious.
--
T.E.D.
http://www.telepath.com/~dennison/Ted/TED.html
Sent via Deja.com http://www.deja.com/
Before you buy.
next prev parent reply other threads:[~2000-02-09 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-09 0:00 Sockets in Apex reason67
2000-02-09 0:00 ` Jim Rogers
2000-02-09 0:00 ` Ted Dennison [this message]
2000-02-12 0:00 ` Simon Wright
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox