Robert Bjarnason wrote:
> -door
> You write a small Java program that logs into VNet server and points its
> "Avatar" to an door VRML geometry that is a door with behaviours for opening and
> closing.
>
> Then when the door is clicked or a proximity sensor sends the click, the Java program
> sends back open/close behaviour request.
>
> This should result in a door that opens and closes @ the same time for connected
>users.
>
> I think that this is possible with VNet today, or am I wrong?
>
>
oh yeah, and another thing, imagine this: a DOOR whose default state is closed,
and user USER1. USER1 enters the world and sees a closed DOOR. USER1 clicks on
the DOOR to open it, and the click event goes to the DOOR bot (somehow) and the
doorbot sends a DOOR.OPEN behavior. USER1's copy of the DOOR opens. now USER2
enters the world. and sees a closed DOOR, since his client never saw the "open"
behavior event, and so his copy of the DOOR does not know it's open.
when i was doing my experimenting, i just happened to have a clickable door
lying around, and indeed it does work this way. it's not necessarily a problem,
though, for example for a game where everyone is required to be present at
the start. it does point out that dumping initial state to the client can
be quite tricky, and it gets really messy for large worlds with lots of fast
changing state...
-cks
