Embedded Files
Beside a local contact lookup for a remote Topic Map / Database / Container or Web Site an Internet lookup server can be used. Thus with the URL
http://lookupdomain/web/lookup?uid=/w3-1340739606989-uid-tm-topic-561/w3-9019278607914-uid-tm-topic-258
it is possible to get from the lookupdomain server a new request with
http://project_host:1701/w3-1340739606989-uid-tm-topic-561/w3-9019278607914-uid-tm-topic-258
If the real location URL contains also the container and topic ID the local domain can be replaced again by the lookupdomain to find the topic, if the project database relocates to another host. The result is an 'ID oriented web architecture' with stable web links.
If the web user visits the page of 'Scott', a link can be shown by 'supports Riverside Project' and behind, the URL containing the UIDs is used. An annotation with the role type ID should be used for typed web links. The type is part of the client view page and not of the link defined by the server.
The addressing schema can be extended to
lookup?uid=/webcontainer/subcontainer/sub.../topic
Due to scalability reasons at least one container ID is necessary. Otherwise the lookup infrastructure nearly needs as much memory as all data resources it should address.
The following subpages show how it works with this site as an example and an established lookupdomain
w3-uid.net.
Thus the following links are location independent:
w3-uid.net Home - http://w3-uid.net/w3-1352468709090-uid-net/w3-1352468709090-uid-net-home
w3-uid.net is a running lookup service on Google App Engine.
Page updated
Google Sites
Report abuse