###########################################################
# filetransferNotes
#
###########################################################
HW Requirements
   1. USB2.0 256 MB memory stick ( thumbdrive ) 
   2. TS7260 board

SW Requirements
   1. CM-II Web Server File Transfer page
   2. Provide download to web browser any or all CM-II configuration files
            - comms/smiCmIpp2.data/def
            - comms/smiCmModem.data/def
            - comms/smiCmLan.data/def
            - devices/smiCmDev_1-16.data/def
            - site/smiCmCfg.data/def
            - users/smiCmUsers.data/def
            - zones/smiCmZone_1-256.data/def
   3. Provide download to web browser CM-II alarm history file
   4. Provide restore defaults to any or all CM-II configuration files
   5. Provide restore defaults to CM-II log file
   6. Provide upload from USB 2.0 thumbdrive files to CM-II filesystem 
   7. Provide different functionality to different user types
     - Admin - upload, download, and restore all files - Comms, 
               Site, Device, Zones, User, Log.
     - Super - upload, download, and restore Site, Device, Zones, 
               User, Log.
     - User - download Log.
     - all can view any file.

UI Requirements
   1. Files when viewable will be viewable through the web browser.
   2. Downloads and log file archives will be provided only through
      the USB port.
   3. Uploads of configuration files will be provided only through
      the USB port.
   4. Uploads shall be verified for parse errors and specification
      errors through the respective system for the configuration file.
      Errors may result in a rejection of the upload, and no changes
      will be made to the system, or upon user approval accepted in a
      partially valid state.
      - e.g. User accounts will be parsed and passwords verified.
        A parse error or bad name or password will not change any
        accounts at all.
      - Zone files will be parsed and validated, then the state of the
        zones will be presented to the user.  Invalid zones will be 
        marked as such, and the user can approve or reject the upload.
      - Discovery files will be parsed and validated.  Discovery will
        then be run.  Any device not found on the uploaded list will
        result in a rejection of the upload.
      - Once files are validated and changes are committed, the new file
        will have a checksum applied.
   5. CM-II shall account for simultaneous upload of discovery and zones,
      and present the user with an overall picture of what the system
      state will be if both are uploaded.



        
