TIMEOUT DURING FILE POST
"Williams, Mark L CIV NSWC PC" <[email protected]> Mon, 20 Aug 2007 13:32:26 -0400
| Newsgroups | gmane.lisp.allegro |
|---|---|
| Message-ID | <2790804CBFD3C749BE6D40CE54CDA5A1037F9591@naeanrfkez06> |
This is a multi-part message in MIME format. ------_=_NextPart_001_01C7E350.13271F80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 ------_=_NextPart_001_01C7E350.13271F80 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7652.24"> <TITLE>TIMEOUT DURING FILE POST</TITLE> </HEAD> <BODY> <!-- Converted from text/rtf format --> <P><FONT SIZE=3D2 FACE=3D"Arial">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?</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Mark L. Williams</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Head, Information Technology = Branch</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Naval Surface Warfare Center Panama = City</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C7E350.13271F80--