| PRESENT  | 
    
      - Jon Hsieh 
 
      - Jon Wildstrom 
 
      - Andy Zimdars 
 
      - Rudy Setiawan 
 
     
     | 
  
  
    | STATUS
     | 
    
      - Andy:
          - DB will have size information (will be accessing CD at Rahal)
 
          - Network will be getting idea of net traffic/load
 
          - We are using Voyager -- Good enough for proof of concept.
 
          - Integrated Rad to be done by Documentation team
 
          - Our RAD has been approved!  We must be good!
 
             
         
         
      - Jon W: 
          - Minutes and documents CVSed.  
 
          - will make sure that HW2 and SDD parts are CVS submitted.
 
         
         
      - Rudy:
          - Reading Network and Events mission statements.
 
          - We provide channels and Events, Network provides all transport
 
          - 1 session creates many channels which disseminate information
 
         
         
      - Jon H:
          - Present DB APIs, and how he thinks DB will work.
 
         
         
     
     | 
  
  
    | DISCUSSION
     | 
    
      - What goes through events? everything.
 
      - We need to try to define events and an event hierarchy.
 
     
    APIs 
      - Authentication: 
          - Talk of being a "moat" around event services.  Otherwise,
            since we don't really interact with authentication, we need little information.  
 
          - We need them to basically provide logon and logoff events.
 
         
         
      - Events/Network: Cannot define becuase of contention with Nework team.
          Nonetheless -- a set of interfaces will be provided that will allow changes to and
        from different event services.
 
      - UI -- 
 
      - DB -- 
          - We need acess to event logs and bogus datasets so that we can test our our
            subsystem.
 
          - Decided that server-side Learning system will learn and send WHAT do update
            messages/events to dealers.  Events queue will be maintained primarily by dealer who
            will have a WHEN to update scheduler locally.
 
          - Need event to let us know when the DBHQ database is upading the PAID server DB.
 
         
         
     
    Fantasy Requirement -- update facility that can prioritize data based on relevance to
    situation and size of portable PAID client.  | 
  
  
    | ACTION
    ITEMS  | 
    
      - Andy 
          - Post to discuss about trying to have other teams notify and communicate through events. 
 
          - Channel guidelines
 
         
       
      - Rudy 
          - Talk to network about push pull situation questions
 
          - settle networks Vocabulary/technology confusioin: sockets = CORBA = RPC?
 
         
       
      - Jon W 
      
 
      - Jon H 
          - Contact DB to get a bogus DB, and information on triggers.
 
         
       
      - Everyone else
          - We need someone to present our part of the SDD (concurrency) to the client on Thursday
            11/5.
 
         
         
     
     | 
  
  
    | CRITIQUE
     | 
    
      - Short notice is bad.
 
      - I miss things when I take minutes.
 
     
     |