Agenda, meeting of Thursday, 28 May 1998

Organization

• Assignment of minutes
• Discussion of meeting time
• Confirmation that everyone is available tomorrow
• Wednesday tea
• Description of appropriate form of minutes
  • Indicate starting and ending times
  • Use asterixes for bulleted items
  • Use plus signs for subitems
  • Feel free to use HTML

Reports

Each member is to report on their experiments done for today. It seems most of you were successful at getting your part done.

Architecture

Do our experiences with the four experiments suggest anything about an appropriate architecture? I will note that there is some clear similarity between the two competing architectures, as we can even have the "compiled .html to .cgi files" be little more than links to clio.cgi.

As we work on designing our logging subsystem, we will need to consider:

• The various fields that clio.cgi (or equivalent) will use
  • "page/url"
  • session id
  • user id?
  • logging category (e.g., we may use the same script to log for multiple "sites")
  • ...
• The log file server. What will communication with that server look like?
• How many "clients" there will be to the log file server

Division of Labor

Note that that there are different ways in which we can divide the labor in the project. We've talked about having one person do the logging subsystem, but it would also be possible to have different people do different parts of the logging subsystem (and, similarly, different parts of other subsystems). What would you prefer?

Today or tomorrow we should select an appropriate week-long project (or projects) for each group member. What we select depends, in part, on our decisions about the best methods of dividing labor.

Note that I may also ask you to work on selected side-projects and sub-projects (which is a typical expectation of the research projects I've been a part of).