× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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).

--Robert


-----Original Message-----
From: wdsci-l-bounces+rdean=landstar.com@xxxxxxxxxxxx on behalf of Joe Pluta
Sent: Mon 3/6/2006 9:00 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] WDSC lockup (was: Rational Updater)
 
We're not having any sort of disconnect.  RSE doesn't "block the UI thread"
on any application other than its own.  In fact, unless I'm grossly
mistaken, there isn't one global UI thread that all programs share; there is
one per application.  That's why one program can lock up and others still
run.

You CAN consume enough resources to make other programs seem sluggish,
especially on an underpowered machine.  This may be what you were
experiencing, I don't know.  But to say that WDSC somehow locks the UI
threads of other applications is imprecise.

Joe

> From: Dean, Robert
> 
> We seem to have a disconnect here.  I understand what you're trying to
> communicate, but you apparently think I'm trying to write that WDSC will
> lock up any PC.  You'll note that I never wrote that.  The point was and
> is that RSE blocks the UI thread.  On my previous PC, this had
> worse-than-usual consequences.  These consequences may have been
> localized to my PC, but that doesn't change the fact that blocking in
> the UI thread is bad design.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.