Concurrency is something that most people who have written web applications know they have to deal with. In GUI based applications, long running actions are often put in their own thread (I remember teaching this years ago when I was teaching Delphi - when the Tdatabase first allowed multi-threading).
But much in the GUI is linear and you simply have to wait for what you want. I don't see a huge impact here except for gamers and processor intensive apps like graphics & number crunching? Richard --- Richard Vowles, Solutions Architect, Borland New Zealand email: [EMAIL PROTECTED] phone: +64-9-9184573 cell: +64-21-467747 other: MSN [EMAIL PROTECTED], skype: rvowles blog: http://www.usergroup.org.nz/blogs/selectBlog.html?id=39769 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, 4 May 2006 6:43 p.m. To: NZ Borland Developers Group - Delphi List Subject: [DUG] Processor speeds and the need for concurrency Hi folks, This article is over a year old but I just happened upon it. It's the first thing I've come across which adequatlely expresses reservations I've felt for a couple of years now that our long paradise of ever-increasing CPU throughput is over. And what that signifies. http://www.gotw.ca/publications/concurrency-ddj.htm cheers, peter _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
