Re: [vrjuggler-info] Shared Data & Vector

[Aron B. <ar...@ia...>]

Eric Maslowski wrote:
> Hello All,
>   I'm working on creating a small abstraction of the shared data mechanism.
> Our applications need to occasionally trigger an event. These events don't
> happen enough to warrant a variable or class for each possible event. Also,
> several are called just once and then never again. Storing info for all of
> these possibilities just seems wasteful.
>   So, I was thinking of just having a vector/list which holds the "events"
> for the current frame. (a la. traditional network messaging - type id +
> char*) The control computer is the only one who updates these messages
> (adding/removing) and each cluster node just checks this queue each frame to
> figure out what happened. Now, I don't see any obvious problems with doing
> this, especially with the new latePreFrame() routine, however, I just wanted
> to ask if anyone can see a situation in which this will come back to bite
> me.
> 
> Thanks
> 
> E.

I can't think of any reason that this would not work.

-Aron