HP3000-L Archives

July 2002, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Wirt Atmar <[log in to unmask]>
Reply To:
Date:
Thu, 11 Jul 2002 13:16:24 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
Greg asks:

> I need to automate a process which seems to defy reliability.
...
>  We could add a pause.
>  But how long is long enough to pause without being too long, such that it
>  delays processing? This requires erring on one side or the other.

The basic rule associated with the design of asynchronous circuits, either in
hardware or software, where you are thinking about waiting some specified
time for a process to complete, but have no assurance otherwise that it has,
is: "Never do it. Never implement an asynchronous circuit. Always find some
way to make the circuit synchronous (i.e., handshake)."

Something like trigger files are going to be the only reliable way to make
this work.

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2