Andrew Piskorski wrote:
I have an Expect script which I'm exec'ing from AOLserver. This
works, and the inefficiency of forking doesn't really matter in this
case. But it's annoying, as it means I can only communicate with the
Expect script via command line arguments and stdin/stdout/stderr.
I'd much rather just have the Expect Tcl API directly available in
AOLserver. But is that in fact feasible? Is there any version of
Expect which can be dynamically loaded into AOLserver (or plain tclsh
for that matter), via 'package require', the modules list in
AOLserver's config file, or some other such mechanism? For AOLserver
3.3, or 4.0?
My guess is that you really should separate expect scripts from
AOLserver. If you really have to, you can create a separate thread,
communicate with it and have it do all the expect commands (to avoid
some of thread safety :).
Although it would be better to spawn another process and communicate via
tcp/ip or perhaps using http (tclhttpd+expect should work quite nice :).
I usually work with a separate thread, for example my antivirus scanner
has a separate thread, which does [open |mks32] and communicates with it.
--
WK
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
