CSS font stacks, developer FAQs & web standards
This page is part of a searchable archive of the Code Style site log. Technical implementation notes that shed light on when, why and how the site has evolved since 2000.
Follow the latest entries to the site log.
Added further mapping of hyperlinks in the HyperlinkFactory class so that links are indexed both by referrer and target URL. Also extended the WebResource class to maintain a map of all referrers, and added methods to the Analyser class to recursively trace browse paths back from a target URL. Methods include a depth argument to prevent endless recursion.
Actions: Ask a question about this post, seek clarification or offer a correction.
Continued work on the new log file analysis package. Created types to represent individual Web pages and hyperlinks amongst them: a Resource interface and WebResource implementation, plus Hyperlink and HyperlinkFactory to register and re-use links. Extended the CombinedLogParser class to extract path and referrer data from log files and create hyperlink objects during the parse, the Analyser application then prints summary statistics on the aggregate usage of links.
Actions: Ask a question about this post, seek clarification or offer a correction.
Started work on a new Web server log analysis package to map browse paths, break-down and trace individual sessions as far as possible. Initially created a pairs of generic interfaces and Web-specific implementations classes, as follows:
Request and WebRequest
Session and WebSession
ServerClient and WebClient
LogParser and CombinedLogParser
Also created an application class Analyser to run the parse and data processing. The first draft CombinedLogParser extracts IP addresses and user agent strings to build a map of Request instances by host address. Sessions are then written to standard output in CSV format.
Updated the font survey results and browser reference table with Firefox version 1.0.6 and Mozilla 1.7.11, which were previously unseen.
Actions: Ask a question about this post, seek clarification or offer a correction.
Find technical implementation notes on all aspects of the Code Style site.
For a summary overview, see the annotated site log contents.
