Comments on: Interaction Blooper #1: Waiting for the User http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/ Longer than a blog; shorter than a book Wed, 07 Jan 2009 01:11:45 +0000 http://wordpress.org/?v=2.6.3 By: Adam Prall http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-114622 Adam Prall Sun, 29 Jul 2007 18:02:50 +0000 http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-114622 I've been evaluating ChronoSync as well because of an online review. According to the features I found in the program and on the company’s website, it’s a great solution—but in reality, it’s actually pretty bad. I have a gigabit ethernet network with a storage-attached 1.5Tb drive and am backing up many gigabytes of data to it. I got up this morning expecting my first sync to be completed, and it was only 25% of the way through step 1 of 5 (about 3% overall) of a 420Gb backup. If I’d done this just dragging folders in the Finder, it would have completed this operation in about 17 hours. At the rate ChronoSync is running, about 1% of my network’s normal speed, it will take about 71 days. No thank you. Goodbye, ChronoSync! I’ve been evaluating ChronoSync as well because of an online review. According to the features I found in the program and on the company’s website, it’s a great solution—but in reality, it’s actually pretty bad. I have a gigabit ethernet network with a storage-attached 1.5Tb drive and am backing up many gigabytes of data to it. I got up this morning expecting my first sync to be completed, and it was only 25% of the way through step 1 of 5 (about 3% overall) of a 420Gb backup. If I’d done this just dragging folders in the Finder, it would have completed this operation in about 17 hours. At the rate ChronoSync is running, about 1% of my network’s normal speed, it will take about 71 days. No thank you. Goodbye, ChronoSync!

]]> By: Mokka mit Schlag » Chronosync: Final Answer http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-14141 Mokka mit Schlag » Chronosync: Final Answer Thu, 07 Sep 2006 18:47:59 +0000 http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-14141 [...] After evaluating Chronosync for a month, the evaluation period is up and it’s time to make a decision. To buy or not to buy, that is the question. I think the answer is no. Chronosync is too slow and too complex to justify paying for. [...] [...] After evaluating Chronosync for a month, the evaluation period is up and it’s time to make a decision. To buy or not to buy, that is the question. I think the answer is no. Chronosync is too slow and too complex to justify paying for. [...]

]]> By: Philippe Lhoste http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-10796 Philippe Lhoste Thu, 17 Aug 2006 14:15:50 +0000 http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-10796 I couldn't agree more... I still have Mozilla 1.7 on my old Win98SE computer and I hate when it asks if it should compress folders, stopping the downloading of new messages until I answer... Then it says it cannot download messages while compressing folders... BTW, I wonder why you use a bold font for your posts, and such big fonts in the whole page. I couldn’t agree more…
I still have Mozilla 1.7 on my old Win98SE computer and I hate when it asks if it should compress folders, stopping the downloading of new messages until I answer…
Then it says it cannot download messages while compressing folders…

BTW, I wonder why you use a bold font for your posts, and such big fonts in the whole page.

]]> By: The Cafes » Eclipse Classpath Insanity http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-10576 The Cafes » Eclipse Classpath Insanity Wed, 16 Aug 2006 12:56:47 +0000 http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-10576 [...] « Interaction Blooper #1: Waiting for the User [...] [...] « Interaction Blooper #1: Waiting for the User [...]

]]> By: Reg Braithwaite http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-10402 Reg Braithwaite Tue, 15 Aug 2006 13:08:37 +0000 http://cafe.elharo.com/ui/interaction-blooper-1-waiting-for-the-user/#comment-10402 Amen! Architecturally, this is often easy to do when you set out to write process-intensive applications. Such applications are often written using the command pattern. Commands (such as copy one file) are generated in a supervisor thread and placed in a queue. Worker threads take commands out of the queue and attempt to execute them. Results can be placed in a queue back to the supervisor, which can report successes and failures asynchronously. This solves the UI problem you describe as well as dealing with situations where there are multiple resources that have different performance characteristics. If you are copying some files to a local drive, some to a network drive, and some to an FTP server, the application should be able to copy all of the local files while the copy to the FTP server is taking place. The overall performance will be faster than using a single thread. Amen!

Architecturally, this is often easy to do when you set out to write process-intensive applications. Such applications are often written using the command pattern. Commands (such as copy one file) are generated in a supervisor thread and placed in a queue. Worker threads take commands out of the queue and attempt to execute them. Results can be placed in a queue back to the supervisor, which can report successes and failures asynchronously.

This solves the UI problem you describe as well as dealing with situations where there are multiple resources that have different performance characteristics. If you are copying some files to a local drive, some to a network drive, and some to an FTP server, the application should be able to copy all of the local files while the copy to the FTP server is taking place. The overall performance will be faster than using a single thread.

]]>