A normal message is between two concrete vobjects. An update message is sent from a concrete vobject to update its replicas. For example, a property sending out a change notification. It's not a "normal" message, because the actual C++ object the message is delivered to is not a concrete Vobject, it's a replica.
Another way of putting it, say we have two object A and B, and with remote replica B'. Normal messaging looks like this: A -> B' -> (network) -> B Now B wants to update its replica. If it's just a normal message, the routing would have to look like this: B -> (network) -> B' -> (network) -> B But obviously that makes no sense, so we mark it as an update message, so the routing looks like: B -> (network) -> B' -> (callback) -> A Which is what we intended. On Wed, Mar 14, 2007 at 08:28:03AM -0700, Ken Taylor wrote: > I'm sure if I spend more time tracing the code i could figure this out > myself, but I'm in a lazy mood... > > What's the difference in the way Messages and UpdateMessages are handled by > the VOS library? Why can't everything be treated as a plain Message? > > -Ken > > > _______________________________________________ > vos-d mailing list > vos-d@interreality.org > http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ]
signature.asc
Description: Digital signature
_______________________________________________ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
