# Message handlers practicality

**URL:** <https://forum.inductiveautomation.com/t/message-handlers-practicality/27698>\
**Category:** Ignition Early Access\
**Created:** [August 23, 2019, 7:36am UTC](https://forum.inductiveautomation.com/t/message-handlers-practicality/27698 "2019-08-23T07:36:18Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [August 29, 2019, 2:43pm UTC](https://forum.inductiveautomation.com/t/message-handlers-practicality/27698/8 "2019-08-29T14:43:33Z")

</div>

> [@betti.francesco](#):
>
> “sendMessage” calls? in this way you could build up some internal collection that couples the message ids to the components that are calling them

Even this would not be 100%, because you can use sendMessage via the Scripting Library. We're tossing around several ideas internally, but it'll be some time before they're finalized and implemented.

Also, as Paul mentioned, we can't construct a list of messageKeys from scripting invocations, because

```auto
system.perspective.sendMessage('UPDATE{0}'.format(self.getSibling('TextField').props.text, payload={}, scope='session')

```

is totally valid, and would result in different message keys when in use.

---

_[View the full topic](https://forum.inductiveautomation.com/t/message-handlers-practicality/27698)._