Hi Joel,

RunScriptCommand is a OLE/COM call, so it's not going over TCP.  I would 
say it's definately a lower-level C call.

--
Bryan

Joel VanderWerf wrote:
> I don't know much about ole... is RunScriptCommand blocking on a tcp
> socket call? If so, it should be possible to wrap a timeout block around
> RunScriptCommand. The timeout block starts another thread. If the
> timeout fires, the blocked call will be interrupted (ruby's thread
> scheduler works well if threads are blocked on socket ops, but not
> arbitrary C functions). You can rescue and clean up the socket.

-- 
Posted via http://www.ruby-forum.com/.