CHANGES
01/16/2001	tgagne@ix.netcom.com
			I created IsdSmalltalkWorker, a worker
			that accepts smalltalk code, evaluates it,
			and writes the result back to the client.

			It was because of this I decided to release the 
			latest version if isectd (with bug fixes).
--------------------------------------------------------------------
This is the README for the second version of the smalltalk 
interface to isectd.  The first one worked too unreliably.

To start the system with smalltalk as the remote execution daemon
I start it after starting isectd.  Whatever order you use, it
must be started before piping a configuration through isdclient.

The configurations will attempt to start the workers, and if
the remote execution daemon isn't there to receive the requests,
isectd will complain, but it won't die.  

If the execution daemon is started late, you can start the workers
by re-issuing the 'start' commands for each worker.

TO LOAD

Isect.st depends on the Headless image thing to be loaded.
I haven't tested it in a while, so  no promises are being made.

NOTES

o	Smalltalk is kind of new to me, so any comments 
	you want to make regarding the code are welcome.  
	Please mail them to tgagne@ix.netcom.com.

o	Eventually, I think it would be swell if I 
	(or someone else) wrote a worker that interpreted
	smalltalk code.  This way, I could use isdclient
	to submit smalltalk to a remote process, and 
	have the reply streamed back to the client.

	Don't you think that would be cool?

o	By creating Smalltalk workers it becomes possible to
	include VisualWorks as part of a piped command
	through isdclient without having the expense
	of loading the entire VM--it's already loaded
	somewhere else.
