No such thing as a small change | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I would suggest that the user issues the request for the zip-file. He is told when to expect it ... he is notified, simply, that the work has been completed. He can now log back on to the web-site to retrieve the results. However he wants to get them. Corporate e-mail systems, (ahem...) sometimes really suck, especially with large things, like, say, zip-files that take twenty minutes to produce. It really amazes me how many otherwise well-intentioned “shops” have forgotten all of the good lessons of “the batch-job days.” Sure, no one needs to go back to //ZIPFILE JOB (123,456),'CREATE ZIP' (although those crufty old days certainly do still exist...), but the notion of doing “intensive” work in a non-interactive setting was, and still is, a very good one. If a shop will actually embrace the notion, it can have a very dramatic difference on many aspects of the work flow. When a computer system becomes over-committed, the performance degradation that results is not linear; it is exponential. It is “hitting the wall.”
“What he means is Old Testament, Mr. Mayor, real wrath of God type stuff. Fire and brimstone coming down from the skies! Rivers and seas boiling! Forty years of darkness! Earthquakes, volcanoes... The dead rising from the grave! Human sacrifice, dogs and cats living together... mass hysteria!” And the only thing that you can do is, “don’t do that.” In reply to Re: keeping connection alive while spending time building a zip file
by sundialsvc4
|
|