Another possible solution (extends (2) above): download all localized text as a single binary data file. The UA client is responsible for providing the correct localized text. This goes beyond events, and applies to all localized text.

Use case: a UA client that acts as a gateway server to another system. The external system may be a large plant operating 24/7, and will have personnel each using a different language/locale. When an operator logs into the system a different language may be used.

The gateway should not have to open a new session for the same data just to get text in a different locale. For scalability the gateway wants to open a single session to the UA server using a neutral locale. It will handle multiplexing the subscribed data to its own clients. For localized text data it will perform mapping the default locale to its client's locale as needed.

related issue was fixed, making this a dupe.