Forcing a driver call to use a specific thread
Mon Oct 29 17:57:57 CET 2001
First off thanks to the OTP team for providing some very nice documenation
to help driver writers :)
I notice from the section at
that calls through the same port will always use the same driver thread. I
also notice the "experimental" use of the key parameter which allows the
driver writer to control which calls must use the same thread.
My question is about the status of the key parameter. The document says it
is reserved and must be set to NULL but there is some nice functionality
behind it.. So
Is this functionality likely to be finished and supported sometime soon?
Or is it finished but has some limitations which may be worked around?
Or is it really experimental, untested and unstable?
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
More information about the erlang-questions