Closed
Description
I have a simple websocket example that I'm trying to implement with rsocket-js (since I'm connecting to a Spring WebFlux-powered websocket endpoint).
This works using plain ol' websockets:
const socket = new WebSocket('ws://localhost:8080/ws/profiles');
socket.addEventListener('message', (event: any) => {
window.alert('message from server: ' + event.data);
});
From the current docs, I figured this is equivalent to the following.
// Create an instance of a client
const client = new RSocketClient({
// send/receive objects instead of strings/buffers
serializers: JsonSerializers,
setup: {
// ms btw sending keepalive to server
keepAlive: 60000,
// ms timeout if no keepalive response
lifetime: 180000,
// format of `data`
dataMimeType: 'application/json',
// format of `metadata`
metadataMimeType: 'application/json',
},
transport: new RSocketWebSocketClient({url: 'ws://localhost:8080/ws/profiles'}),
});
client.connect().subscribe({
onComplete: (socket: any) => {
socket.requestResponse();
},
onError: (error: any) => console.error(error),
onNext(payload: any) {
console.log('onNext(%s)', payload.data);
},
});
However, I don't get any console logs when I trigger a new websocket event.
Related: does rsocket-js support sending an authorization header in the request like socket.io-client does?
Metadata
Metadata
Assignees
Labels
No labels