Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.programming Subject: Re: long tasks Date: Wed, 03 Oct 2012 09:07:54 +1300 Lines: 13 Message-ID: References: <82c0ce54-e033-4196-bf6c-7c9272e117d4@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net jC94IcWx74uTQaMdYU2QfAeceiFPkZN4nVmA06Ch5am9+ciLXsKugWmLihw/KTt3O3 Cancel-Lock: sha1:HN1D6959Fx12t38i7uH7981FSas= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:12.0) Gecko/20120423 Thunderbird/12.0 In-Reply-To: <82c0ce54-e033-4196-bf6c-7c9272e117d4@googlegroups.com> Xref: csiph.com comp.programming:2282 On 10/03/12 03:36, bob wrote: Please wrap your lines! > I've noticed that one of the things that makes real-world programming difficult is time-consuming tasks (or potentially time-consuming tasks). Some examples are downloading a file& reading from a database (maybe). > > Usually these are handled in the real-world by things like multi-threading and callbacks, which can quickly turn messy. Are there other strategies that can maybe handle these things more simply? Sit and wait. Alternatives such as threading only add value if there is useful work that can be done while the slow operation is in progress. -- Ian Collins