[Top][All Lists]

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

Re: open socket with listen() and still have command line available?

From: Brian W.
Subject: Re: open socket with listen() and still have command line available?
Date: Thu, 24 May 2007 15:50:19 -0700 (PDT)

from reading several of your posts on the listen function it seems that you
are kind of fixated on your TCL stuff. Because there are many more uses of
octave besides embedding in TCL, your short answer could have been "you are
right, listen is useless unless you want to have reduced octave


Paul Kienzle wrote:
> On May 23, 2007, at 11:05 AM, Brian W. wrote:
>> Hi,
>> I have a question about the listen(port,...) function as described by  
>> 'help
>> listen' or at
>> miscellaneous/doc/listen.txt?view=markup
>> .
>> Is it possible to open a socket via listen(port) and still have the  
>> standard
>> input stream connected to the octave process?
>> I have tried all combinations of 'fork'|'nofork' and  
>> 'debug'|'nodebug', but
>> whenever I have called listen(port), any commands typed into the octave
>> command line are ignored (actually the prompt is missing, too).
> Normally I talk to the octave session directly from the TCL console.
> Since the application forks on each connection there is no benefit from  
> interacting with the listening octave.
> You could probably program it so that multiple processes interact with  
> the same session, including a simulated octave console, and have the  
> illusion that the octave which started the listen is continuing, but I  
> see no need to do that either.
> - Paul
> _______________________________________________
> Help-octave mailing list
> address@hidden

View this message in context:
Sent from the Octave - General mailing list archive at

reply via email to

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