Has anyone looked at the issue of a file transfer failing during a POST operation when operating under Webactions? It seems like a sufficiently large file could fail for a number of reasons. I'd actually like to be able to time-out the operation. For instance, if you're buffering input, a (really) short wait for each buffer-full should be sufficient to indicate a need to abort the transfer from server end, especially if you have a smallish buffer. If you don't do that under control somehow, how do you determine that things have collapsed? Consider a big transfer that the user gets tired of and cancels, or backs out of. Then the session could/should still be alive but the status of the data that was uploaded is undetermined. How does that get handled now, and is that sufficient?

Mark L. Williams
Head, Information Technology Branch
Naval Surface Warfare Center Panama City