objects l 1 l 2 l 3 are located on three servers 100 102 104 flow between objects is controlled by switch 106 layout object l rendering object r and user interface ui are located at the client 108 table 3 describes the events that take place in response to a user inputting a uri objects not in active use are shown in dashed lines were the load distribution or quality of service qos to require their use e g to server other clients or to take up the load in the event of a server failure these inactive objects could instantly be brought into use as they are installed and ready 0071 fig1 depicts the above system dynamically reconfiguring after one server 102 has failed switch 106 directs layout to the layout object l on the browser client 108 alternatively the switch could have directed the layout request to the inactive layout object l 2 on server 104 0072 fig1 depicts one embodiment in which latency data is propagated through the system by attaching a timecard timesheet parameter 110 to each request each of the five processing stages fetching parsing layout rendering ur keeps track of its start and finish time and simply records on the timecard the time u03b4 it spent processing the request in the example shown in fig1 the fetching process took 4 time units the parsing and layout processes each 3 time units the rendering process 4 time units and the ui process 3 time units the timecard is also used to record the total accumulated time u03c3 u03b4 spent by each stage 0073 fig1 shows the result after a second request is processed the total accumulated time for fetching is 7 time units for parsing 6 time units.