On Fri, 18 Apr 2008 22:16:23 -0400, Jim Bohnsack [EMAIL PROTECTED]
wrote:
It really does depend. I'd love to send you a softcopy but it was
written before I could have saved you one. I have a typewriter written
carbon copy.
If you have a scanner you could make a JPG image of each page.
: Monday, April 21, 2008 7:54 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Setting a reliable MINIMUM connectivity latency?
On Fri, 18 Apr 2008 22:16:23 -0400, Jim Bohnsack [EMAIL PROTECTED]
wrote:
It really does depend. I'd love to send you a softcopy but it was
written before I could have
Of Brian Nielsen
Sent: Monday, April 21, 2008 7:54 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Setting a reliable MINIMUM connectivity latency?
On Fri, 18 Apr 2008 22:16:23 -0400, Jim Bohnsack [EMAIL PROTECTED]
wrote:
It really does depend. I'd love to send you a softcopy
On Fri, Apr 18, 2008 at 11:19 PM, Mike Walter [EMAIL PROTECTED] wrote:
We've determined an average workstation latency (simply using PING) for a
workstation far, far away as being about 380-400ms.
But we don't know what it would be like to actually WORK on that workstation
day-in and
On Apr 19, 2008, at 3:03 AM, Rob van der Heij wrote:
On Fri, Apr 18, 2008 at 11:19 PM, Mike Walter
[EMAIL PROTECTED] wrote:
We've determined an average workstation latency (simply using PING)
for a
workstation far, far away as being about 380-400ms.
But we don't know what it would be
For 3270 you may find bandwidth sooner to be an issue. Long time ago I
worked on 300 bps. When someone then put a 'FULLREAD ON' in some
shared XEDIT profile (because IBM recommended it) I had plenty of
time to think about adequate punishment...
Jim is very right about expectations. Many
Mike Walter writes:
We've determined an average workstation latency (simply using PING) for a
workstation far, far away as being about 380-400ms.
But we don't know what it would be like to actually WORK on that
workstation day-in and day-out. Most of the work would be in support of
Mike ...
Maybe you need to re-think the problem.
What if the interactive part could be handled locally
with file synchronization carried out in the background?
If you need the remote also for execution, that could be
driven over SSH with commands stacked onto the session(s).
Something like this:
RSYNC is nice because it (normally) only copies what has changed.
-- R;
We've determined an average workstation latency (simply using PING) for a
workstation far, far away as being about 380-400ms.
But we don't know what it would be like to actually WORK on that
workstation day-in and day-out. Most of the work would be in support of
Linux for System z servers.
Mike--The answer is it depends (Bill Bitner) but that answer is also
contained in a paper I wrote in about 1970 while working on my MBA at
the University of Chicago. It was entitled Psychological Aspects of
Terminal Response Time and it earned me an A for the course.
It really does depend.
On Fri, Apr 18, 2008 at 5:19 PM, in message
[EMAIL PROTECTED], Mike
Walter [EMAIL PROTECTED] wrote:
We've determined an average workstation latency (simply using PING) for a
workstation far, far away as being about 380-400ms.
That's a bit on the high side for non-blocked keyboard I/O.
12 matches
Mail list logo
