![]() ![]() Refreshed/updated periodically), such as the volume meter level of anĪudio receiver entity to be displayed by its user interface agent.Ĭertain Mbus messages (such as queries for parameters or queries to Some messages will have a rather transientĬharacter conveying ephemeral state information (which is Have different reliability requirements (which are typically derivedįrom their semantics). RFC 3259 A Message Bus for Local Coordination April 2002įurthermore, Mbus messages exchanged between application entities may Mechanisms (defined in Section 6) and by providing a flexibleĪddressing scheme (defined in Section 4). The Mbus protocol as defined here satisfies these differentĬommunication needs by defining different message transport Response exchanges between any local server and its clients. Intended recipients, e.g., messages related to media synchronization.įinally, there may be messages that are directed at a single entity:įor example, specific configuration settings that a conferenceĬontroller sends to a particular application entity, or query. Or there may beĪny (application- or message-specific) subgrouping defining the Messages may also be targeted at a certain applicationĬlass (e.g., all whiteboards or all audio tools) or agent type (e.g.,Īll user interfaces rather than all media engines). ![]() State changes, etc.) may need to be sent to all local applicationĮntities. Information, floor control notifications, dissemination of conference Local coordination of application components requires a number ofĭifferent interaction models: some messages (such as membership Other possible scenarios include the coordination of applicationĬomponents that are distributed on different hosts in a network, for Is conducted with a stand-alone IP telephone can be dynamicallyĮxtended to include media engines for other media types using theĬoordination function of an appropriate coordination mechanism.ĭifferent individual conferencing components can thus be combined toīuild a coherent multimedia conferencing system for a user. Group of application modules: For example, an IP telephony call that It can also be used to implement tightlyĬoupled conferences enabling a conference controller to enforceĬonference wide control within an end system.Ĭonferencing systems such as IP telephones can also be viewed asĬomponents of a distributed system and can thus be integrated into a Synchronization between media streams or to configure entities In loosely coupled conferences such a mechanism allowsįor coordination of application entities, e.g., to implement Those taking part in application sessions that belong to the sameĬonference. Located but otherwise independent application entities, for example In a variety of conferencing scenarios, a local communication channelĬan provide conference-related information exchange between co. One example where a simple coordination infrastructure can be useful: The implementation of multiparty multimedia conferencing systems is RFC 3259 A Message Bus for Local Coordination April 2002 1. 33 12.2 Registry based parameter storage. 29 11.4 Procedures for Senders and Receivers. 23 8.2 Calculating the Timeout for Mbus Entities. 23Ĩ.1.4 Adjusting the Hello Message Interval when the Number ofĮntities decreases. 23Ĩ.1.3 Adjusting the Hello Message Interval when the Number ofĮntities increases. 21 8.1.1 Calculating the Interval for Hello Messages. 20 8.1 Hello Message Transmission Interval. ![]() RFC 3259 A Message Bus for Local Coordination April 2002 6. 5 1.4 Terminology for requirement specifications. Specifies the Mbus protocol, i.e., message syntax, addressing andġ. Multicast scope is limited to link-local multicast. ![]() Top of IP multicast and is specified for IPv4 and IPv6. Peers, subject based addressing, reliable message transfer andĭifferent types of communication schemes. The Mbus provides automatic location of communication The local Message Bus (Mbus) is a light-weight message-orientedĬoordination protocol for group communication between applicationĬomponents. Distribution of thisĬopyright (C) The Internet Society (2002). Not specify an Internet standard of any kind. This memo provides information for the Internet community. Request for Comments: 3259 TZI, Universitaet Bremen RFC 3259: A Message Bus for Local Coordination ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |