# \[Question\] Session Events scripting?

**URL:** <https://forum.inductiveautomation.com/t/question-session-events-scripting/21678>\
**Category:** Ignition Early Access\
**Created:** [January 3, 2019, 11:32pm UTC](https://forum.inductiveautomation.com/t/question-session-events-scripting/21678 "2019-01-03T23:32:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![brian.mills](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brian.mills/32/6348_2.png) [@brian.mills](https://forum.inductiveautomation.com/u/brian.mills)\
**Post date:** [January 3, 2019, 11:32pm UTC](https://forum.inductiveautomation.com/t/question-session-events-scripting/21678/1 "2019-01-03T23:32:43Z")

</div>

It was previously stated that all scripting will occur on the gateway. That being the case, are the Perspective\>Session Events scripts the exception to that rule? (For all types of session events, but specifically barcode scans…)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 3, 2019, 11:45pm UTC](https://forum.inductiveautomation.com/t/question-session-events-scripting/21678/2 "2019-01-03T23:45:51Z")

</div>

Browsers don’t run jython. The module SDK can supply true client-side scripting as part of a new component, but it will be javascript, not jython. All events generated on the client that connect to jython will make a round trip. The offline functionality for collecting scans & data entry will defer all jython scripts until reconnected. Offline functionality is a bit fuzzy still.

---

<div class="post-metadata">

**Author:** ![PerryAJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/perryaj/32/3281_2.png) [@PerryAJ](https://forum.inductiveautomation.com/u/PerryAJ)\
**Post date:** [January 3, 2019, 11:55pm UTC](https://forum.inductiveautomation.com/t/question-session-events-scripting/21678/3 "2019-01-03T23:55:13Z")

</div>

Nope! Phil’s beat me to the punch, but he’s right - session event handlers _execute_ on the gateway, including all the mobile device data collection handling stuff. Now the event/data that triggers the script may (obviously) occur somewhere else, but ultimately/eventually, the collected data is sent to the gateway for handling and script execution. From the perspective of a single device, offline scans are sent to the gateway as a ‘batch’ in the order they were collected. On the gateway, they are handled in the order they are received.

---

<div class="post-metadata">

**Author:** ![brian.mills](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brian.mills/32/6348_2.png) [@brian.mills](https://forum.inductiveautomation.com/u/brian.mills)\
**Post date:** [January 3, 2019, 11:58pm UTC](https://forum.inductiveautomation.com/t/question-session-events-scripting/21678/4 "2019-01-03T23:58:48Z")

</div>

Ok, That’s what I was thinking…but I was hoping there was some"back end" magic IA added (I’ve had to change my reply a few times due to the other replies 😁)

I would think that it would also follow that all transactions to/from the gateway/device would have an increasing delay if poor signal strength is encountered until the offline point is reached or the signal picks back up in strength.