On Tue, Mar 06, 2007 at 04:16:26PM +0200, Jamshed Qureshi wrote: > Since i know more of twapi than tcom, i opted for a test to see if > this will work. During a twapi forum chat with its developer he > pointed out that twapi is not test with threads. and this brings me > again to square one.
If you need the twapi functionality from AOLserver, I'd just try it. If twapi's author believes that twapi is written in a mostly thread-safe manner (e.g., no global variables), but he's just never tested it in multi-threaded use, then it seems a reasonable bet that any thread-safety problems you encounter won't be that bad to fix. (I've no idea how much of twapi is Tcl and how much is Windows C code, though. C is of course more work to fix than Tcl.) Also, MS Windows seems to be more thread friendly in general than most Unix systems. (Probably because theads were the latest trend back around when Windows NT was being designed.) My limited Windows programming experience suggests that most (or at least more) APIs on Windows are already reentrant, so you're less likely to run into mysterious thread safety problems when mixing multiple libraries into a single multi-threaded application. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
