1. C++ application could write to a database.
   The webpage could read from this database.
   * Separation of Concerns - yes
   * Great for higher scale solutions

2. C++ application could write to a file.
   The webpage could read from this file.
   * Separation of Concerns - yes
   * You want to have direct access to the data,
     for reading or writing
   * Great for testing
   * Great for medium scale solutions

3. C++ program also generates the webpage with
   a library, and can update the webpage itself.
   * Separation of Concerns - no
   * This is a monolithic architecture
   * Great for high performance solutions

4. C++ application would write to a socket
   and the webpage read from the socket.
   * Separation of Concerns - yes
   * Good for high performance solutions
     (removes the middle man)
   * Good for small scale solutions
   * Needs a package for handling sockets
   * Webpage has to be simple

5. Python could be used to glue or deploy
   everything together.
   - start the webpage (Django or Flask)
   - start the C++ application (intfMonitor)
   - interconnect the two.
     * communicates with the webpage through Django or Flask
     * communicates with intfMonitor through sockets

   * Separation of Concerns - yes
   * Enjoys the speed of sockets with the flexibility of
     Python (or Django)
   * Deployment of the application with the webpage

6. The CGI-BIN interface between applications and webpage (defunct)