Posted by Brian Levantine on May 11, 2010 at 17:24:44:
In Reply to: Re: Read request status posted by Bill Morgan on May 10, 2010 at 11:56:30:
Because Qantel polled their terminals they were able to always "know" when a read was requested even without the terminal being read-enabled. Normally, read is enabled only when the program actually performs a read. For our purposes, polling (which is a non-no for Windows apps) is not practical due to the overhead created by it - especially for CometAnywhere users. Our solution, albeit a not-so-good solution was, upon determining that the program was in a loop (determined by 50 consecutive calls to the STS function) to poll for status, we would send the read-enable to the terminal which would then allow the program to get the read status when it was posted. The down side of this (magic number 50 aside) is that once read is enabled (unlike Qantel), the buffer is read even if you don't want it. One solution that would avoid possible compatibility issues for other users is to add a mnemonic code that would allow you to manually read-enable the terminal which would eliminate the need for the loop. Alternatively, you can use the code I sent you to read-enable the terminal - which executes instantly by the way - no task breaks required. FYI - Since Comet98 was released, you're the first to notice this anomaly. We'll discuss this further to see if there's a better way to handle this problem.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.