+
+ <p>I have coloured the commands in an attempt to make it clear as to what goes on, where and why.
+ <span class=cmd>These coloured lines are miscellaneous commands</span>, the <span class=expect>things
+ that are this colour are the strings I am looking for (what I am "expecting")</span>
+ and the <span class=send>things that are this colour
+ are the commands I am going to make when I see the "expect" strings in the input</span>.</p>
+
+ <p>The script starts by setting the timeout to 15 seconds, then starts
+ the connection. It is <b>important</b> to note that, in the case of
+ an ax25 connection (usually) this will be the callsign of the <i>first hop</i> along the
+ route that you are going to take to the destination, so this will be typically the callsign
+ of your local node.</p>
+
+ <p>You will notice that the script waits until it sees the left hand string
+ of the pair and <b>only then</b> does it send the,
+ string on the right
+ hand side. This is called a <i>State Machine</i>.</p>
+
+ <p>A <i>state machine</i> "walks" through a conversation (in this case) looking
+ for "states" (in this case particular strings) and then performs some
+ "action" (usually some kind of connect command for the type of system
+ you are trying to navigate). When one "state" "fires" (detects the string
+ are looking for), it sends the command associated with that state and then
+ moves onto the next "state", in our case: the next line.</p>
+
+ <p><b>PLEASE NOTE</b>: the colouration in the above example is for illustrative purposes
+ only, the debug output is all one colour.</p>
+
projects / spider.git / commitdiff