Changes between Version 4 and Version 5 of InterModuleCommunication


Ignore:
Timestamp:
Aug 13, 2009, 5:38:44 PM (8 years ago)
Author:
mgraff
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InterModuleCommunication

    v4 v5  
    1616 * A group join request is performed to join a group.
    1717 * Only the members of the group may transmit to it.  (Should this restriction be removed?)
    18  * Group names are created using a principal/instance@host format.  The principal is the "group name" (such as "ZoneNotify" for zone notification messages), the instance may be specified or left wildcarded, and the host may be specified for local-to-this-host groups.
     18 * Group names are created using a principal/instance@host format.  The principal is the "group name" (such as "!ZoneNotify" for zone notification messages), the instance may be specified or left wildcarded, and the host may be specified for local-to-this-host groups.
    1919 * When subscribing, multiple subscriptions may occur for the same group but with different instances.  For example, an auth server configured to serve zone1.example.com and zone2.example.com may choose to only subscribe to those instances.  A "zone compile" module may listen on the wildcard, as the data it works with is identical regardless of the instance.
    2020 * The use of principal/instance@host is a convention that each data producer/consumer of that data needs to agree on.  This allows flexibility in the API but applies a convention tin how people actually use the API.