WebSocket client

[WebFreak001]

It would be nice if there would be an WebSocket client for connecting to externals servers and redirecting that output to the user and process it on the server.

[dariusc93]

@WebFreak001 you mean like for the client-side (eg javascript) or a vibe.d websocket client that connects to another server that has websockets?

[WebFreak001]

No I want the vibe.d server to connect to a websocket server. There is also TCPclient so why not WebSocket client

[dariusc93]

@WebFreak001 well websocket was not made for server-to-server connection. It shouldnt be to hard to implement but to me honestly do not see the point. maybe @s-ludwig could talk explain?

Also could you explain what youre trying to do? Maybe there is a different solution. I honest feel that the websocket should be slighly rewritten.

[WebFreak001]

I want to make a chat bot for hitbox (which uses websockets). I used nodejs before but now i switched to vibe.d because not having actual classes in javascript (Not prototype stuff, JSON or new Function) is really annoying. (I tried TypeScript but the compiler is bugged and now I really hate it and I dont like coffeescript or dart)

[s-ludwig]

This would be relatively straight forward to do, mostly reusing the existing code. I can't personally promise a date when I would have the time to actually implement and test it, though.

[dariusc93]

@WebFreak001 is the websockets are for javascript for client-side to talk to the server and youre trying to talk to another server at the same time, you could look into using the rest interface. I use the rest interface to send data back and forth between the servers (I would use tcp for that but i decided to just use rest for now). Like @s-ludwig said, it should be straight forward. I dont think it should be to hard to do though, but I moved to vibe.d because I did get tired of node.js. I normally try to stick with system languages like go, d, rust, c/c++.

[etcimon]

The client basically does the inverse of the server negotiation: https://github.com/rejectedsoftware/vibe.d/blob/master/source/vibe/http/websockets.d#L69

I would suggest to follow the RFC.

As for the Websocket class and all the rest, I don't think there's any difference. Probably a 100 lines of code missing there.

[s-ludwig]

If not even much less!

[etcimon]

The only particularities I can see is this

Clients MUST choose a new masking key for each frame
(the data from the server to the client is not masked).

WebSocket clients verify that the server included one of the values that was specified in the WebSocket client's handshake.

[etcimon]

Usage would look like this:

void handler(scope WebSocket ws) { .. }

requestHTTP("http://....", (scope req) { handleWebsocket(&handler, req); });

The HTTPClientRequest will need a switchProtocol

[yannick]

would be great to have this in.
this could also be useful to build a rpc system over websocket e.g. with msgpack-d

[WebFreak001]

Just found out about connectWebSocket, seems to be implemented already