I think it largely depends on the implementation.
If you create an IO add-on it would work like:
- Send specially formatted message to OH
- OH IO add-on parses the message, determines which Item the message is destined for, and postUpdate or sendCommand (or however an Item is updated or commanded from a binding) to that Item.
No Rules are required.
If you create a regular binding it would work like:
- Send a specially formatted, but the format is something you come up with yourself, message to OH
- OH binding sendCommands the message to an Item bound to the Telegram Item’s Incoming Channel
- User creates a Rule to parse the contents of the specially formatted message and does something with the information (e.g updates or commands other Items)
I definitely see advantages and disadvantages to both approaches. But the IO binding approach fits in more closely with OP’s original use case of messages like:
<ItemName> <New State>. It also requires less work on the user’s part as the format of the messages is predefined and no Rules are required.
In short, it could be implemented as either an IO add-on or as a traditional binding, but I think an IO add-on would be a better choice.