From: reason67@my-deja.com
Subject: Sockets in Apex 3.2.0b
Date: 2000/02/09
Date: 2000-02-09T00:00:00+00:00 [thread overview]
Message-ID: <87sclh$oe4$1@nnrp1.deja.com> (raw)
I apologize if this gets posted twice. After about an hour of my post
not showing up, I decided to post again.
I wrote a binding to the Sockets. I am using Apex 3.2.0b Duo on Solaris
2.6.
I have written test code that uses a non-blocking socket for the client.
On the call to connect, I see interesting results:
1) In the non-threaded model, everything works as expected.
2) In the threaded model, if I have only one thread (no tasks),
everything works as expected.
3) In the threaded model, if I attempt to do the connect in a task,
funny things happen (errno is not set, it determines if a server
is not started immediately instead of returning that in the
select)
Is there anyone out there familiar enough with the Apex Threaded
Run-time system enough to explain to me what causes this?
---
Jeffrey Blatt
Sent via Deja.com http://www.deja.com/
Before you buy.
next reply other threads:[~2000-02-09 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-09 0:00 reason67 [this message]
2000-02-10 0:00 ` Sockets in Apex 3.2.0b Richard Toy
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox