# GatewayHook getRPCHandler Implementation **URL:** \ **Category:** Module Development\ **Created:** [July 26, 2023, 11:40pm UTC](https://forum.inductiveautomation.com/t/gatewayhook-getrpchandler-implementation/76980 "2023-07-26T23:40:23Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 26, 2023, 11:50pm UTC](https://forum.inductiveautomation.com/t/gatewayhook-getrpchandler-implementation/76980/3 "2023-07-26T23:50:28Z")
This was asked/answered [here](https://forum.inductiveautomation.com/t/mimic-multiple-python-package-namespaces-in-single-module/54506) as well. Basically, you get one RPC handler, but that _doesn't_ have to be the same object as your script modules, so multiplex it out however you want. Also for your consideration: for years now we (IA) no longer add new scripting functions to Designer / Vision Client scope and relay them over RPC. We only add new scripting functions to Gateway scope. --- _[View the full topic](https://forum.inductiveautomation.com/t/gatewayhook-getrpchandler-implementation/76980)._