Approach to long-running connections to external services | Laravel | Page 1

errant plinth Nov 30, 2024, 4:45 PM

I am making an e-sports tournament managing platform, where users can play in fully automated matches in various games. As such, I will need to connect to various external API's, sending HTTP requests but also listening to web sockets. I'm trying to figure out how I would even approach building such a feature. I'm certainly not looking for complete solutions, but just a sense of a direction of how to do this. I already have a service which can make authenticated http requests, and i've looked into listeners, but i'm not sure if either of these are designed to have these kind of long-running websocket clients

urban pulsar Dec 1, 2024, 4:30 AM

websockets are long-running connections

they typically send ping and pong messages back and forth to keep it open

I'm not sure if I'm understanding correctly

Does the server need to connection to an external service via web sockets and keep it open?

Or do you mean User of your app needs to be connected to web socket?

#Approach to long-running connections to external services