<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Stefan Andersson wrote:
<blockquote cite="mid:BLU134-W4950353EE89D6B6FDE4A0CD5C70@phx.gbl"
type="cite">
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>Kind of crazy idea here, but how is 'landmarks' actually
stored on the server and used by the client? Shouldn't we be able to
store grid and region endpoint in a landmark?<br>
<br>
I mean, if the landmark contains the region name, it could just as well
be stored with target grid and/or region endpoint in it as well?<br>
<br>
If the client only uses an uuid, it should be requesting that
conversion from the region, which could in turn use the users home grid
servers to resolve the uuid request into more metadata - as the
landmark was originally created on that grid. (yes, that could, in
theory, mean that person A clicking on a landmark in region B would
cause B to talk to home grid C that will access originating grid D to
resolve the actual endpoint and things like that, but hey - think of
the possibilities!<br>
<br>
</blockquote>
<br>
There's lots of possibilities, I just found out doing this. The map
search, for example, was a wonderful surprise, since the viewer sends
whatever we type there verbatim to the server. So we can type anything
we want and interpret it on the server-side...<br>
<br>
I haven't looked into landmarks yet, but it's quite possible that it
does the same.<br>
<br>
<br>
</body>
</html>