Revision f4a60a9b nest/proto.sgml

View differences:

nest/proto.sgml
69 69

  
70 70
<p>At any time, the core code can ask the protocol to shut itself down by calling its stop() hook.
71 71

  
72
<p>The <em/core state machine/ takes care of the core view of protocol state.
73
The states are traversed according to changes of the protocol state machine, but
74
sometimes the transitions are delayed if the core needs to finish some actions
75
(for example sending of new routes to the protocol) before proceeding to the
76
new state. There are the following core states:
77

  
78
<descrip>
79
	<tag/FS_HUNGRY/ The protocol is down, it doesn't have any routes and
80
	doesn't want them.
81
	<tag/FS_FEEDING/ The protocol has reached the <tt/PS_UP/ state, but
82
	we are still busy sending the initial set of routes to it.
83
	<tag/FS_HAPPY/ The protocol is up and has complete routing information.
84
	<tag/FS_FLUSHING/ The protocol is shutting down (it's in either <tt/PS_STOP/
85
	or <tt/PS_DOWN/ state) and we're flushing all of its routes from the
86
	routing tables.
87
</descrip>
88

  
89 72
<sect1>Functions of the protocol module
90 73

  
91 74
<p>The protocol module provides the following functions:

Also available in: Unified diff