I noticed that I am having a difficult time identifying if and when a token is removed
or added through the muscle interface.. I am sure that many others are having the
same issue.. yes you can use the callback with MSCCallbackForTokenEvent() but this
API can cause all sorts of threading issues. especially if you try and cancel them while
they are waiting
It occurred to me that a simple way to identify tokens coming and going would simply be to add a field to the MSCTokenInfo structure with that would be a somewhat unique hash (or better yet a CRC-16) maybe based on the slotName + tokenId + The time the token was first seen in the slot..
this way you can poll the tokenList periodically with MSCListTokens() and just
look if the hash has changed for a given slot..
vin
_______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
