Next: Overview of Files and Up: Client/Server Communication Previous: Client/Server Communication   Contents   Index |
".pesto.commstat"
, see Figures 6.1 (p. ),
6.2 (p. ), and 6.3 (p. ). The
pesto-taco daemon is based on code from the TACO user guide [12].
Figure 6.4 (p. ) shows the data flow. The arrow from the socket interface to the linkd daemon should not be taken too literally - it is more complicated than so, see [11]. An overview of the files are given in Section 6.4.
The system naturally uses TACO implicitly when it (TACO) is running, since the TACO system handles the forwarding of all IP and UDP packets to and from the client when weakly connected, see [11].
Next: Overview of Files and Up: Client/Server Communication Previous: Client/Server Communication   Contents   Index |