Re: new display file features

Actually I'd think some of those chat sessions and the accompanying server 
loads might rank with a room full of clerks banging on terminals. There's 
a server(s) somewhere handling AOL's Instant Messenger service and that 
can not be a light load.  But thats all beside the point. 

The AS/400 works and works well.  The customer is the one that should 
decide whether or not to implement performance pigs like sending 
keystrokes to the cpu. 




Please respond to MIDRANGE-L@midrange.com
Sent by:        owner-midrange-l@midrange.com
To:     MIDRANGE-L@midrange.com
cc: 

Subject:        Re: new display file features

Booth,

I agree that there is a change in the paradigm.

To compare apples to apples, get one AS/400 to echo keystrokes, get
another to file serve, get another to application serve, get another as
a communications server, etc.

To have 20 people keying into a chat session and 200 others lurking does
not put the same load on a server that has 200 people doing order entry,
cash receipts, payables entry, production scheduling, shipping,
receiving, inventory control, payroll, etc.

IMHO, one of the failures of OV/400 was the performance degradation when
you had too many people choking the system with keystroke activity.

The shift in paradigm may be to blast the file down to the client
machine and let the client handle file positioning and keystroke
echoing. And the GUI.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---