Interactive Web Architecture

Architecture

LowLat uses available bandwidth, either during idle periods on low-speed channels or excess capacity on high-speed channels to support server-side preloading of the receiver-side cahhe. In Lowlat, the conventional client/server interaction of the Web is augmented with a client-side "Filter Cache" and a server-side "Pump Preloader". The client uses the filter as a local proxy, encapsulating web requests to the filter. The pump is used as a server-side cache, requiring relocation of the server to another port. The filter and pump interact as in the conventional Web, using conventional request-response on the well-known port. The filter allows presending on a separate port (plod), and the pump allows feedback (updates) on filter cache hits to direct the presending on a different port (updt).

The Lowlat architecture is showed here:


     +--------+  8081 +--------+    8082 +--------+    80 +--------+
     |        |-ec r->|        |---req-->|        |--req->|        |
     | browser|       | filter |         |  pump  |       | server |
     |        |<-resp-|        |<--resp--|        |<-resp-|        |
     +--------+       |(proxy  |         | (proxy |       +--------+
                      | /cacge | 8083    | /cache |
                      | server)|<--pres--| server)|
                      |        |         |        |
                      |        |    8084 |        |
                      |        |--updt-->|        |
                      +--------+         +--------+
  redirect to proxy   (here.loc)         (here.remote)
  at here.loc:8082
      <-----------client----------|   |----------server----------->

                    FIGURE : LowLat architecture

Go back to the LowLat home page. / Go back to the ISI home page. ISI Logo

This page written and maintained by Amy S. Hughes.
Please mail me any problems with or comments about this page.
Last modified May 13, 1997.