> RE: Looking thru Portals
> i think that this is best handled by the WWWInline node (someone correct
> me if i have misinterpreted the node) because this allows the description
> of the portal to be designed by the host that the portal links to. the
> portal object is retrieved from the target host with all associated
> information (like the hyper-link call itself). this, of course is one
> way, unless the target host has a portal back at the portal entry point.
> this permits cool registration in many realms to one entry point.
Hmmm. This make me feel somewhat better. I can see how this would work.
The problem, still, is that you have to have the cooperation of the
viewed space. Otherwise, when you walk through the door and turn around,
there may be nothing there to return to. It's like a Web page that not
only can contain a link to a remote page, but requires that the remote
page contain a link back to it, at the same point. Without such
cooperation, a portal can't be created.
Maybe we should stick to Trekish transporter technology for links. You
decide where to go, or accept coordinates from a local object, and then
<whirr-thrumm-sizzle> you're there. No viewing (except maybe on your
tricorder screen) of the target space until you're there. Maybe a link
could look like a video display. You can see a small view of the remote
space, and if you want to go, you just jump through the screen. I kind of
like that. It kind of draw the user in, so to speak.
---
Andrew C. Esh mailto:[email protected]
Computer Network Technology [email protected] (finger for PGP key)
6500 Wedgwood Road 612.550.8000 (main)
Maple Grove MN 55311 612.550.8229 (direct)
<A HREF="http://www.mtn.org/~andrewes">ACE Home Page</A>