Ethan,
It seems like you're looking for a programmatic solution to a physical
security problem. In the end, your most viable solution will likely be to train
Mr. Goodguy to remove the key the same way he needs to remember his ATM card
after a withdrawal. I've seen programmatic work-arounds
Right off the bat, you need to consider concurrency issues. Depending on the
size of your user base and level of activity this could become a major issue.
In the end, why hold an open connection for 15 minutes just to process 20-30
transactions that take 20-30ms each? Just better (under most
esigndrumm.com=DwIFAg=shNJtf5dKgNcPZ6Yh64b-A=HSbgyt8GFSyWQ53Nxworjip-dgIKnMlPBkQ0VGj7tYk=w7VxdOhlxCY27A_sfaFCxntsWMG8ZDA3nukN6fBstsA=JzvStr8fa_OyNaHOUe0Xp8_o6aDzZSgZ6OXyEk6WyIM=
>
>
>
>
>> On Mar 5, 2017, at 6:19 PM, Arneson, Joshua <joshua.arne...@mssm.edu> wrote:
>>
>> R
