Re: WDSC lockup (was: Rational Updater)

I misinterpreted it because you wrote "My previous PC (a Pentium 4 2.6 GHz
w/2GB RAM) would completely lock up WDSC *and* Windows if an action blocked
in the UI thread," when what you meant was "if WDSC blocked its UI thread,
not only would the application lock up, but so would Windows."

If you don't see how that could be misinterpreted, then feel free to
attribute it to my reading, rather than to your writing.  <smile>
 
Joe


> From: Dean, Robert
> 
> With all due respect, what you've written shows exactly what the
> disconnect was.  No knowledgeable person would think that an app can block
> the system UI thread (we're not talking OS/2's single kernel msgq after
> all), so I didn't see how what I wrote would be misinterpretted.
> 
> The bottom line is that the RSE blocks the WDSC UI thread without the
> courtesy of at least a progress bar with a Cancel button.  It should
> provide that at the very least.  As an Eclipse 3.x plugin, it should also
> provide a "Run in Background" button on said progress bar.  On my previous
> PC, this behavior had more serious consequences than it does on most PCs
> (I blamed the PC, which is why we never opened a PMR on this issue).