Check out the new USENIX Web site.

Logical to Physical URL Binding

A given Web++ client applet must first find a list of physical URLs that correspond to replicas of every logical URL found in each HTML resource. The list can be found in several ways:

A drawback of the first scheme is that the client may have to incur an additional network round trip to bind a logical URL to a physical URL. The network round trip can be saved by caching the binding information on the client, but such a solution leads to several problems on its own (the interplay of dynamic replication and cache consistency being the most prominent one). Since one of the goals of document replication is to improve the response time perceived by clients, we rejected this option.

The second scheme does not lead to any extra overhead for the client to bind a logical URL. Moreover, since the majority of URL requests can be predicted from the hyperlinks embedded in the HTML text, it makes sense to optimize the binding scheme for this case. The drawback of this scheme is that it is not clear how to resolve logical URLs which are directly supplied by the end-user via e.g. File $\rightarrow$ Open browser menus.