[17487] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Platform Assumptions: what does it mean to assume threads?

daemon@ATHENA.MIT.EDU (Sam Hartman)
Mon Jan 30 12:35:40 2012

From: Sam Hartman <hartmans@mit.edu>
To: krbdev@mit.edu
Date: Mon, 30 Jan 2012 12:35:25 -0500
Message-ID: <tsld3a1xfdu.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu



So, assuming that a threading library is available and that for example
an application can take advantage of threads seems reasonable.
Similarly, assuming that threads headers for Windows or POSIX threads
are available seems reasonable.

However even when threading is enabled, libk5support tends to use weak
references to threading symbols and not always assume they are linked
into a given application context.

What are we actually talking about doing if we change our threading
assumption?
_______________________________________________
krbdev mailing list             krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

home help back first fref pref prev next nref lref last post