# Perspective Client, additional WebSocket connections

**URL:** <https://forum.inductiveautomation.com/t/perspective-client-additional-websocket-connections/86765>\
**Category:** Module Development\
**Tags:** perspective\
**Created:** [March 4, 2024, 3:25pm UTC](https://forum.inductiveautomation.com/t/perspective-client-additional-websocket-connections/86765 "2024-03-04T15:25:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [March 4, 2024, 3:25pm UTC](https://forum.inductiveautomation.com/t/perspective-client-additional-websocket-connections/86765/1 "2024-03-04T15:25:51Z")

</div>

Are there any SDK functionalities for creating additional WebSocket connections between a Perspective client and the gateway?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 4, 2024, 4:31pm UTC](https://forum.inductiveautomation.com/t/perspective-client-additional-websocket-connections/86765/2 "2024-03-04T16:31:06Z")

</div>

No. Everything in the architecture assumes that, by definition, a connected Perspective session is communicating over the single extant websocket.

This sounds like a bit of an XY problem - why do you want to set up a second connection?

---

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [March 4, 2024, 5:25pm UTC](https://forum.inductiveautomation.com/t/perspective-client-additional-websocket-connections/86765/3 "2024-03-04T17:25:57Z")

</div>

I’m looking to stream high frequency time series data to the client, and I’d like to do it “out-of-band” from the rest of the system and in a non-JsonObject format.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 4, 2024, 5:31pm UTC](https://forum.inductiveautomation.com/t/perspective-client-additional-websocket-connections/86765/4 "2024-03-04T17:31:12Z")

</div>

Fair enough. The websocket we create in `ChannelStore` is just the standard browser WebSocket API, so it shouldn't be too challenging to create your own. You'll have to implement your own websocket _servlet_ in your module's code - that'll probably be more complicated, especially tying back contextual info from the frontend to the backend to plumb everything through.