Re: Using tn5250

["Robin Wenham" <robin.wenham@xxxxxxxxxxxxxxxxxxxxxx>]

Hi Marek.  Yes, that is the obvious thought - but wouldn't that then
trigger the TCP acknowledgement that Holger was discussing?

There is not a problem with wireless coverage holes in this area: it is
well covered.

Thanks for your reply.

Regards

Robin Wenham
Absolute Network Solutions Ltd



-----Original Message-----
From: linux5250-bounces@xxxxxxxxxxxx
[mailto:linux5250-bounces@xxxxxxxxxxxx] On Behalf Of Marek Bajon
Sent: 09 February 2010 10:54
To: Linux 5250 Development Project
Subject: Re: [LINUX5250] Using tn5250

When I'm hearing about WiFi and "X Wait" my first thought is "lost 
packets".
When you press ENTER (or any function key), the data entered is sent to 
your server and then a response (display refresh) is sent back to the 
workstation from your server. If a packet is lost in either direction 
the communication is "out of sync" - the display waits for an answer 
from the server which is not coming because:
a) the server did not get any / complete data from the workstation;
b) the server got data from the workstation and sent an answer, but the 
answer was totally / partially lost in the network.

I have had similar problems when connecting over a slow and unreliable 
GSM network. A proper solution is to improve your WiFi reliability. A 
quick and dirty walkaround for the case a) above is to reset the display

(left Ctrl key - the "X Wait" should disappear) and press the ENTER or 
function key again - this sends the data again to the server.

Good luck!
Marek