roland@jts.com (Roland Knight ) (05/23/91)
It seems there is a bug in the wire service provided with TNT2.0. The problem
occurs when sending postscript to the server during a syncronization period.
The postscript code executed during this period is done so manually by the
following line in wire_Sync:
{ currentfile token pop exec wire_SyncExit { exit } if } loop
This works fine unless the code being executed contains procedures since these
procedures will be exec'd immediately rather than put on the stack. The
problem can be avoided by putting an extra set of {} around the procedures but
will obviously only work if the code is executed within a sync period. This
problem also only occurs when wire_Sync is called from the listener process
(in this case the calling process simply blocks and is woken up at the end
of the sync period). I haven't checked but I assume a similar problem will
occur when executing delayed code after a sync period.
Can someone suggest a solution to this problem?
Thanx,
Roland Knight
JTS Computer Systems
{yunexus | uunet | geac | torsqnt}!roland@jts.com