Update Activity protocol to use a resourceId #65
Labels
breaking
The resolution creates a breaking API change
client
Issues related to the client
enhancement
New feature or request
server
Issues related to the server
Milestone
Activities currently use a string identifier when sending messages. This is somewhat inefficient. In the model subsystem we map user defined string identifiers to int32 resource ids, which are more compact. We should do the same thing in activities.
Breaking Change
This will be a non-backwards compatible change in the protocol, but has not API changes.
The text was updated successfully, but these errors were encountered: