RC/C: this would be a server (or possibly a set of servers) thats most
basic function is to keep track of the objects that exist in the realm.
another function is the ability to have rules. akin to the laws of
physics, these would be the Realm Laws (corny i know). these rules would
govern whether multiple objects were allowed to see, touch, hear or
interact with one another. (on the Street, avatars were allowed to pass
thru one another. this is sometimes desirable, sometimes not) (only
certain users are allowed) (realm is for browsing only, users dont ever
see one another {VRML 1.0}.) (limited visibility) (etc.)
Entities: dynamic objects that can act without being directly acted upon. a
door is not an entity, an avatar is. when we talk about tracking
objects, the processor and bandwidth considerations are mostly due to
entities (bots and users mostly). static objects require very little
bandwidth.
A VR without Registration.
welcome back broadcast protocols! how else do you become aware of
objects with in the same virtual space? either there is some thing that
keeps track of where everything is (RC/C) or you have to tell everybody
in existence where you are (DIS 2.0?). DIS right now maxes out at
250-500 entities (this running on sgis and t-1 and better) because it is
broadcast based (everybody gets all the updates). the next rev of DIS is
supposed to be mcast, and they are looking at 10k to 30k of entities.
that is quite a jump. i dont think that most realms would have to track
that many entities simultaneously, but even if they did, part of the
coolness would be the fact that the RC/C could alter the rules a little
to adjust for heavy loads. (lower LOD, limiting actions, delaying
updates, etc.)
more stuff:
VRWorld--- easy say easy do. definitely do need indexes and a geographic
index is great idea. (maybe more than one) it just becomes another Realm.
browser--- definitely want to be able to open a location manually (one of
the things that irritated me about Snowcrash) and browse back and forward
and bookmarks.
Reality Check--- whoa back. dont make the spec to echo reality, make
the spec so that the implementation can echo reality. if you want a door
to go both ways, both realms need to agree that they want a mutual
connection. (like WWW, links dont need to go back, that is handled by
the browser remembering.) though i do think that the binding idea merits
looking at. remember we can create a new paradigm here.
Wish List--- i still think this is a good idea. so i will volunteer to
accept everybody's wishes and compile them. these are the big picture
far out ther type wishes that we ussually dont want to think about
because its beyond us to implement them.
Thanks to all
jzbl