04-13-2005
9,926,
461
Join Date: Aug 2001
Last Activity: 26 February 2016, 12:31 PM EST
Location: Ashburn, Virginia
Posts: 9,926
Thanks Given: 63
Thanked 461 Times in 270 Posts
I don't understand how you are using a mouse in conjunction with an ascii terminal. Please explain how that works.
If you are using an ascii terminal, it would take a lot of work to do that. Unix is deeply full duplex at it's heart. If you do "stty -a", you will probably see "echo" rather than "-echo". That means you type a character and it goes to the host which echos it on the screen. Since you are using telnet and therefore psuedo terminals, you can ignore xon/xoff problems. But most people want echoe on so that an erase character is echoed as backspace-space-backspace. The INTR character (usually cntl-C) sends a SIGINT immediately. EOF (usually cntl-D) immediately sends an EOF. SIGQUIT, job control, line erase, the list goes on and on. You are not going to hammer the unix terminal driver into your mold easily. If you succeed, all telnet sessions will be affected. Ditto anything else that uses psuedo terminals. Many unix programs will not function at all, vi comes quickly to mind. Others will not work very well.
Unless your users are bouncing off a satellite or two, I rather doubt that full duplex operation is the problem anyway. What happens when you do other stuff, is everything slow, or just your app? I sometimes need to access boxes in other parts of the world. I get pretty decent response except when I bounce off a satellite. Then I type a character and sometime later it appears. I type a line and wait for it to appear before I can hit return. I admit that linemode does start to look attractive in that environment.
If you are using a telnet client, your platform could run other clients. One option might be to go to a web based application. You would have a html server on the aix box, and the users would use netscape or whatever. Another option is to write your own server and write your own clients.