You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL; DR: Please consider adding a HTTP server (that is CORS aware) in addition to the socket server.
I was trying to use LiveSplit with a web browser based game via a Web Extension. Extensions can't open socket connections. Chrome apps can, but a browser app didn't seem appropriate for my project. So I ended up writing a thin Go wrapper to proxy HTTP to Socket, that ignores CORS, and ignores socket responses.
Whatever was sent as the PATH of the URL is used as the socket command. Using form data, etc, would be fine, too. This solution worked quite well for my use case. I had to grant permission to the domain in my extension, but if the proxy served a CORS header like Access-Control-Allow-Origin: * it should just work without a domain permission. If a simple HTTP server was setup as part of this live split extension, then it would be really easy to build LiveSplit integrations for any browser based web game.
The text was updated successfully, but these errors were encountered:
I'd appreciate the same. I am using an app that runs alongside the game I am speedrunning (specifically, a DPS Meter for an MMORPG). This app allows a bit of customization in that it can perform actions based on events. One of those events is an event that I want to use to automate splits. However, this app I am using doesn't support opening socket connections, but supports HTTP requests.
TL; DR: Please consider adding a HTTP server (that is CORS aware) in addition to the socket server.
I was trying to use LiveSplit with a web browser based game via a Web Extension. Extensions can't open socket connections. Chrome apps can, but a browser app didn't seem appropriate for my project. So I ended up writing a thin Go wrapper to proxy HTTP to Socket, that ignores CORS, and ignores socket responses.
From my extension, I'd call it like this:
Whatever was sent as the PATH of the URL is used as the socket command. Using form data, etc, would be fine, too. This solution worked quite well for my use case. I had to grant permission to the domain in my extension, but if the proxy served a CORS header like
Access-Control-Allow-Origin: *
it should just work without a domain permission. If a simple HTTP server was setup as part of this live split extension, then it would be really easy to build LiveSplit integrations for any browser based web game.The text was updated successfully, but these errors were encountered: