> You should think of each terminal command line as simulating a separate run > of the program you are modeling.
That is my understanding too. Therefore I guess the only way I can communicate sensibly via Terminal with a daemon listening on a port is via something like netcat. As per your example, or one of the examples given by: man nc. This is precisely where the usage of NSTask is hazy to me, and the documentation doesn't seem to help (or else I can't read it properly). I'm going to look for more sample code. On Mon, Nov 9, 2015 at 8:10 PM, Raul Miller <[email protected]> wrote: > On Mon, Nov 9, 2015 at 3:04 PM, Ian Clark <[email protected]> wrote: >> However I don't yet know how to converse via NSTask with a daemon >> through a port. I need to find a tame daemon that will talk to me >> nicely via Mac Terminal, which I can then try to handle via NSTask. >> Then I'll feel more confident about conversing with a long-running >> jconsole process. > > I think you have conflicting (internally inconsistent) requirements here. > > You should think of each terminal command line as simulating a > separate run of the program you are modeling. > > Thanks, > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
