Module Hierarchy

• driver: NEEDS REVISION
  • driverapi: This is an api for driver stuff.
  • engine: Holds the Engine class which manages the following things:
  • event: Holds the Event superclass and a few subclasses that are used in the driver.
  • filesystem: This module should abstract the mud from the filesystem.
  • manager: Managers manage things.
  • network: This is the network module which holds the MasterServer and the Connection objects and handles all socket interface things.
  • utils: This has a series of utility functions that aren't related to specific classes in the application.
• startup: Starts up Stringbean.

Class Hierarchy

• driver.event.Event: The event superclass.
  • driver.event.HookEvent: When information needs to be passed to registered functions of a hook, this allows us to defer execution of that spam event into its own event horizon.
  • driver.event.InputEvent: The InputEvent handles all incoming user input.
  • driver.event.KickEvent: This is a KickEvent for the repo thread which just makes sure everything is running squarely and such.
• driver.manager.Manager: Base manager class for managing things in Stringbean.
  • driver.network.MasterServer: The MasterServer handles all the incoming network connections and holds a series of Connection objects.
• driver.network.Connection: The connection object handles dealing with the user on a socket level.
• driver.utils.PriorityQueue: This is a pretty basic priority queue.