Quote:
Originally Posted by DaWei
No doubt you are correct. It's been 3 years since I used it, and the brain cells don't put off that many sparks, when rubbed together, anymore.
Let me generalize. I used it in a fully cooperative atmosphere. I didn't fire it up unless the clients asked me to. I then required them to give me a current IP (all of them had dynamic IPs), and we set up the passwords. They had the option of terminating the process at any time merely by halting the service.
I felt that if they were in need, they could communicate with me by email or telephone. Usually, we were in contact by telephone at the time the connection was being made. This method totally precludes the necessity of having timers or retries. One just handles it verbally.
|
Well, the only reason I brought this up is in the event there is some kind of rare network communications issue. I'd wanted to have a backup plan, and I also didn't want the program to appear to be connected when it may not be. I want confirmation, doubling as a mechanism to prevent people from clicking the "Begin Session" button I've made first, instead of clicking the "send message" button to notify me of their need in the first place. Just wanted to make the software idiot proof. I wouldn't be surprised if someone clicked on the "Begin Session" button, and just walked away waiting for me to call them or something.