For static web sites, a record in the access log denotes a single browser request and server response transaction. The transfer of the resultant 'page of html' is an atomic operation.
For Busview this model does not hold. When a browser visits the Busview home page (http://busview.org), the html code for this url contains a tag which directs the browser to download and execute a Java program, namely the Busview program. A program run like this is called an applet.
When running, the Busview applet itself makes requests for further resources from the same web server (these requests and their responses go via the browser but logically it is the applet and not the browser in charge. The reason to use HTTP for all applet-server traffic is to work in the presence of firewalls). Some requests are for files: map files, pattern files, route description files, file of prenamed locations. However, the real-time Avl stream of MetroKC buses is not a file. When the applet requests the url 'AvlServer', what comes back from the server is a non-terminating stream of bus data. This stream transfer terminates when the user quits the applet. Only then, in HTTP terms, is the response complete. Thus, only then can the web server log the 'time' of the response and the byte count of the response. Hence the time stamp for the avl stream responses in the access logs are for the stream finishing, but no record is available for stream opening time and thus duration cannot be measured.
Recognising this fact, some special Java code on the server side DOES make a note of stream open and close times and can thus attempt to define stream durations. Analysis of this data is not possible for a web log analyser such as Analog, which treats each record as an independent 'hit'. Stream durations are not included here.
Nevertheless, a lot of info is available from the access logs and most of it is provided below. Note the distinction between a 'browser' making a request and the Busview 'applet' making the request. From a web/system administrator, the distinction is meaningless, it's all bytes on the network!