Connecting to Neoroute with WebSocket
No matter what client SDK you use, this guide will teach you how to connect to your server using a WebSocket transporter.
Creating the client
Before opening the actual connection, you need to create a client (this is the object you’ll be using to send requests).
This is an abstraction we put over the actual connection since you could also be connecting to the server in a different way. The actual message you send is the same between WebSocket and HTTP.
// Import both the transporter (client version) and the client package.
import (
"github.com/Liphium/neoroute/client"
"github.com/Liphium/neoroute/client/transporter/websocket"
)
// ...
// 1. Create a new client (there are more options, we just showcase the most important ones)
c := client.NewClient(client.Config{
// The ErrorHandler will be called for every error that happens inside of the client.
//
// Errors like that aren't returned from requests, like invalid events, are also returned
// through here which is why we recommend definitely using this for WebSocket.
ErrorHandler: func(err error) {
log.Println("WebSocket error", err)
},
})
// 2. Create a new WebSocket transporter
transporter := websocket.NewWebSocketTransporter(c)// Import @liphium/neoroute-ts
// TODOConnecting to the server
Since WebSocket has persistent connections, you need to actually connect to the server using the Connect function (or whatever it is called in your SDK, look below).
// 1. Parse the URL to your server
url, err := url.Parse("http://example.com")
if err != nil { /* handle error */ }
// 2. Call the connect function with your URL
done, err := transporter.Connect(url)
// ^ done is a channel that will return something when the connection is closed, by any means.// TODOClosing the connection
If you want to close the connection you established, you can use the Close function (or equivalent).
// Might return an error when something went wrong during close.
err := transporter.Close()// TODOFrom now
Depending on what SDK you use, you can now send requests to your server or receive events from your server over the WebSocket connection. Click on any of the links to learn more about those capabilities.