bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ncurses on pipes


From: Robert Lemmen
Subject: Re: ncurses on pipes
Date: Wed, 13 Jun 2007 15:44:34 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

hi bob! cool to see you again!

On Wed, Jun 13, 2007 at 09:22:09AM -0400, Bob Rossi wrote:
> I'm wondering if there is a different way to solve this problem. This isn't
> an attempt to change your program, but perhaps a different way to look
> at the problem. If someone is using a telnet client, they already have a 
> working pty on there end.
> 
> On the server side, you also have a pty (stdin,stdout). If you fork/exec
> a child process (which could be the ncurses application) to deal with
> the request, wouldn't that just do what you want without involving the
> pipe or socket?
> 
> I've seen this done before several times.  For instance, the
> sourceforge.net compile farm does this. Also, take a look at
> ascii star wars, 'telnet towel.blinkenlights.nl'. I believe that's how
> they must have solved this problem. Is that what you are looking to 
> achieve?

this is very basically what i want to schieve, but i don't really
understand your approach. if you are aiming at just using a telnet
server and running a UI client program there for each connection (as has
been suggested off-list): i fear that this will get expensive if you
have many clients. if you are talking about something else: please
explain.

apart from the "how do i..." part of this, i really don't understand why
a tty is needed here. is this only because of the mechanism that
determines the capabilities of the terminal? if this is so: is there a
way to supply these capabilities myself so it will work with a non-tty?
or is there something else involved? somewhere on the net i found a text
that gave the hint that output buffering might be a part of the problem
as well...

cu  robert

-- 
Robert Lemmen                               http://www.semistable.com 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]