--- [EMAIL PROTECTED] wrote:
> A single connection can only be used by a single thread at
> a time. If you have multiple threads running at the same
> time, they each need to have their own connection.
>
> If you are not running on a Linux 2.4 kernel, then you can
> pass connections from one thread to another. So thread A
> can do a little work, then hand the connection of to
> thread B to continue. But thread A and thread B should not
> try to use the same connection at the same time.
>
> The reason for this should be obvious.
Nothing is obvious in threadsafe APIs. It means different things
to different programmers.
Hypothetically, a library API could safely clone a connection without
the knowledge of the user using mutexes where appropriate, or use
a threadsafe work queue approach - you never know.
You have to either rely on the author's documentation, or examine
every line of code in the library.
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for
today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
