prefect
Home Engineering Audio Biking Publications Photo Gallery Personal Info
DACS: Service Providers
 
  next up previous contents
Next: Main Application Up: Functional Design Previous: Functional Design   Contents

Service Providers

Figure 108 depicts the functional flow of a typical DACS service provider. The exact nature of a provider depends on the specific application, but the overall structure is the same for all providers.

Figure 108: Functional flow diagram of a typical DACS service provider.
\begin{figure}
\psfig{file=sw/service-flow.eps,width=6in}
\end{figure}

When the service is instantiated, it initializes itself and establishes itself as a TCP/IP server. Upon proper contact from the client, q2q, the program enters a loop, waiting for commands from the client and servicing requests. This loop continues until the client drops the connection. When the connection is dropped, service providers should return to the state in which they wait for a connection from a client. All running functions should stop and return to a default state if this happens.

Steve Richardson 2000-07-06
Table of Contents

[PDF] [Whole document in PDF 1.9MB]

[more photos and information]

 
Page last modified:
Copyright © 1993-2000 prefect - All Rights Reserved.