but that might also just be the Workers interface, not easy to tell as all i get is "Error communicating with origin server echo.websocket.org"

hmm i got

expected cert != nullptr [0 != nullptr]; TLS peer provided no certificate

in the playground when connecting to echo.websocket.org

Maybe try

http

or

ws

?

http

seems to work

i dont see any issues with echo.websocket.org's cert tho

other ws services work fine with

https

might just be their implementation

ill test it with other services

I managed to get a working websocket between two Durable Objects, so it can be done.

see #783765338692386886

Ahh yes. I'm not entirely sure of the use cases now though - any worker created websocket is still subject to the request context, so you would need a long lived (websocket?) connection to establish a... long lived connection?!

The above thought does raise a question (maybe that has been answered but I can't find it on search) - is a DO with an established external WS connection subject to the same CPU / subrequest limits as a normal worker?

subrequest limit is still 50 on a normal Worker, unsure about DO

I can confirm the subrequest limit is the same on DO

Who do I have to bribe/kiss/etc to get into the DO beta? 🧐

Please DM and I will send Doge and or kisses

Hey Dana, if you already applied online, just know there's a long waiting list to get into the beta. But the good news is the storage team is working quickly so DO can move to open beta soon. Appreciate your patience

Ok, if you change your mind about bribery or flattery, let know 😉

🤔

I'd like to second this... I'm willing to name an unborn child after whoever lets me beta DO. It won't be my child, but I'll find one somewhere...

Continued from DMs with @albert-zhao > I have a question about Durable Objects: can they be used for proxying WebSocket connections into TCP connections? > Specifically, currently I’m building a browser application that needs to connect to a server over TCP. Since this can’t be done in the browser, we currently have a proxy server set up which the client connects to over WebSocket; and then the proxy does the TCP Connection. > > This creates latency issues (proxy server can be far away from both ends), so we’re wondering if we can switch over to Cloudflare to potentially resolve that. Is this possible, and, if it is, can we be given access to Durable Objects?

The Workers platform broadly does not let you create raw TCP connections at this point in time; we strictly only allow

http

and

ws

(websocket) connections

Any chance of it being allowed in the near future?

Or, is there another product that does allow this?

Not at the moment, but someday we hope to have TCP Workers

Got it, thanks.

future announcement Matthew tweeted about👀 ?

nah that would be a huge project, creating a worker that could access raw TCP data stream. There's more than enough work for the team, especially with DO 😉

Would be cool to implement an online type-racer competition through DO