Hi,
During some testing of the Sun version of PCSClite we noticed
some SCARD_E_SHARING_VIOLATION errors in SCardReconnect().
A co-worker pointed out that winscard_clnt.c was patched (2475) in the
open source code to make SCardReconnect() loop (re-try) when
SCARD_E_SHARING_VIOLATION occurs, thus masking the error.
That looks like a workaround for something. But does it mask the
error a bit *too* earnestly?
I'm wondering: Why is there not some sort of re-try maximum
in that loop to keep it from looping infinitely without letting the
application know there's an issue, and why isn't there some sort
of time delay to throttle down the rate to keep it from spinning too
fast?
Also, I notice there is no such workaround in SCardTransmit().
I assume maybe there's a good reason to handle it differently in
the two API calls, but I just want to find out if it was a conscious
choice to add it to one and not the other, or not.
Thanks,
Paul
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
