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



Adding to yours, as long as there's only one distressed person at any
one time, kicking people off (or just giving them less system time) may
work but if you have a dozen distressed people (or hundreds), it's not
effective since you can only steal resources from some many other
processes and then you became the nasty so and so that wrote a slow
program.

For interactive systems, response time is king and you have to have
efficiency in mind when you do interactive programming.

Matt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Monday, August 15, 2005 11:15 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Efficiency vs effectiveness (WAS: Force EOF in a Subfile)

I liked that reply.  :)  May I add to it?  



Using your story, lets focus on what is effective, not what is
efficient. 
You have a distressed person out there, quite possibly in danger.  When
that
bell rings the machine better go into "lets take care of this person
fast"
mode.  That is the only issue.  Response time becomes paramount.  Forget
efficiency, cut through the clutter, get responses fast, whatever the
cost
in efficiency.  If you have to kick off the bill collectors, kick em
off,
and don't even  stop to apologize.  But give them response time.  Thats
effective but certainly not efficient..
<snip>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.