You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tagged message API uses a tag and a mask to identify messages. However, applications are really using the tag space as a collection of independent fields. For example, 32-bits may represent the message, 16-bits the source address, and 16-bits as a group address. By exposing the use of the fields to a provider, it enables additional optimizations within the provider. For example, a provider could maintain separate queues, to greatly improve search times. Define a mechanism by which the app and provider can communicate the number of fields and their size.
The text was updated successfully, but these errors were encountered:
The tagged message API uses a tag and a mask to identify messages. However, applications are really using the tag space as a collection of independent fields. For example, 32-bits may represent the message, 16-bits the source address, and 16-bits as a group address. By exposing the use of the fields to a provider, it enables additional optimizations within the provider. For example, a provider could maintain separate queues, to greatly improve search times. Define a mechanism by which the app and provider can communicate the number of fields and their size.
The text was updated successfully, but these errors were encountered: