DN639601749

Subject: Re: Expect: dislocate and WWW - DN [1]

Don Libes <libes@nist.gov> - 27 Jun 2000 - comp.lang.tcl

 Your use of Expect's dislocate is ingenious.  Thanks for sharing that!

 Did you modify dislocate or are you actually calling dislocate
 unchanged?  The UI is a very simplistic thing - made for interactive
 control.  So I wouldn't be surprised if you ripped it out.  Otherwise,
 dislocate is just fine for your purpose.

 If I were to write dislocate again, I'd use sockets instead of fifos.
 I used fifos because the socket command didn't exist back then.  Or
 maybe I just didn't have enough confidence in it.  Or maybe I just
 wanted to find some excuse to use a fifo.  Can't remember now.  (I
 wrote dislocate 7 years ago -- eek!)

 Don

 Albert XinJiang <albertjiang@yahoo.com> writes:
 > I am trying to write a web interface for an interactive unix
 > command-line program.  The goal is to maintain an "interactive session"
 > with the server-side program, through a series of HTML forms.  My
 > current solution is to use the disloate script that comes with the
 > Expect package.  I use dislocate on the server side to spawn the
 > program,  interact with it, and then disconnect it to the background. At
 > the next page visit,  I can call dislocate to reconnect to the process,
 > interact with it according to the html form inputs, then disconnect it
 > and so on.
 >
 > My question is:  is this a good/solid solution?  cause dislocate was not
 > designed to do Web-related stuff....
 > Has anyone done a similar project before?  Any help appreciated.
 >
 > Albert