The subdirectory illustrates a number of ASX framework features for a
sample Stream application called the Event Server.  The Event Server 
works as follows:

1. The ./Event_Server/event_server executable, when started, will
   create two SOCK_Accepter endpoints, which listen for and accept
   incoming connections from consumers and suppliers.

2. The ./Event_Server/Consumer/consumer application may be started
   as "consumer -p 10000 -h hostname", where 10000 is the consumer
   port and "hostname" is the name of the machine the event_server
   is running on.

3. Likewise, the ./Event_Server/Supplier/supplier application may be
   started as "supplier -p 10001 -h hostname", where 10001 is the 
   supplier port and "hostname" is the name of the machine the
   event_server is running on.

4. Once the consumer(s) and supplier(s) are connected, you can type
   data from the supplier window, which will then be routed 
   through the Modules/Tasks in an event_server's Stream and
   end up being sent to the consumer(s).

5. What makes this example particularly interesting is that
   once you've got the hang of this basic architecture, you can
   "push" new filtering Modules onto the event_server Stream
   and modify the application's behavior *without* greatly 
   affecting its functionality.
