> Date: Fri, 26 Nov 1999 11:25:04 +0100
> From: Ingrid Melve <Ingrid.Melve@uninett.no>
...
> Joe Touch promised to send outline of architectural requirements to
> the list.
Here goes.
The architecture consists of three basic components: server, proxy, and client.
The conventional web architecture defines server-client interaction.
Clients connect to servers based on the URL of the request. Network-level
services are assumed to route requests from client to server.
This (WREC) architecture addresses proxies, and their effect on that architecture.
In this new architecture, we need:
- a way to include proxies in the routing of requests
i.e., a way to route requests through proxies
- a way to maintain the proxies
e.g., to keep them consistent
(do we need anything else?)
I'll propose secondary architectural components as follows:
- proxy inclusion
a way to include proxies in a conventional proxy-less deployment
- request forwarding
a way to direct a request towards an appropriate proxy,
e.g., via policy, observation of availability, etc.
(i.e., like IP forwarding)
- request routing (like IP routing)
- request route computation
a way to generate appropriate routes according
to some metric
(i.e., like IP route computation)
- request route exchange
a way to configure the routes of proxies, clients,
and other network elements
(i.e., like IP route exchange)
There is the issue of bootstrapping this configuration;
ala BOOTP, DHCP - i.e., how does one start route exchange
with nothing configured a-priori?
There are standard mechanisms: manual (set a single location)
and well-known address (e.g., fixed port, broadcast message).
(?? is it possible that responses will equivalently be forwarded?
is there utility to that? I.e., to force where things are cached?
should the architecture include that, even if not yet developed?)
- cache consistency
a way to unify the view of what is cached between
sets of proxies
- cache group discovery
a way to determine the association of sets of caches
- cache content exchange
a way to see what is in the others' caches
- cache unification
a way to unify or update the content of a cache
??
Joe
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:27 MST