Hacker News Reader

Comment by mmastrac | Hacker News Reader

As part of my first couple of months of work at Deno, I wrote the new Deno.serve implementation that's being stabilized here. It's based on a thread-local slab that is wired into Hyper 1.0 (which is an amazing Rust webserver and nearing release).

This gave us solid support for HTTP/2 in Deno itself -- you can start a full webserver on a TLS socket and start talking fully-compliant HTTP/2 in just a couple of lines.

It's an interesting challenge to get this to cooperate with V8 in a performance way and we're continuing to work on it while keeping the code as maintainable as possible. The implementation will continue to evolve as we design better and faster interfaces between Rust and V8. The cool thing is that this is all going into open-source projects, either in Deno itself, rusty_v8 or V8 itself.

Happy to answer any questions.

View on HN

Does it have HTTP/3 features like WebTransport?

Not yet, but we are keeping our eyes on HTTP/3. There are a few good options for us to integrate it, but we want to make sure we do it right (and meanwhile figure out the right way to expose HTTP/2 features that aren't available yet).

Sounds like sales speak, nodejs isn’t even there yet.

There are like three different http/3 implementations in Rust, used in real ways. Even if they don't want to write their own, there's a lot of choice out there.

Does streaming work? Server-sent events?

Everyone's interested in SSE again thanks to serverless and Open AI's API

Open AI's API is using SSE to stream results?

It has a "streaming" mode (non-SSE, traditional long http requests") and many developers are choosing to forward chat data to end users with SSE (maybe to get around browser http request timeouts).

Both of these definitely work. I'm on my phone right now so finding references is a challenge, but you can stream either of these ways (or use WebSockets) using Deno.serve.

So how do I get the SSL certificate in there, does it come with it?

I found this:

https://deno.land/manual@v1.35.0/runtime/http_server_apis#ht...

I would personally use letsencrypt and then pass the cert/key into the Deno.serve call, though I am curious now if there is a more integrated solution and I'm going to dig into it a bit.

Use Caddy.

Yes, I too am too lazy to learn nginx, certbot or whatever those things are as well.

Edit: I really am. Why downvote?

I got you boss. Cheers to laziness

Laziness is the Mother of Invention

That's awesome, any automatic HTTPS (ideally by default)?

Yep. As long as you give Deno.serve a certificate and private key and you get modern TLS, HTTP1 and HTTP2.

Oh, sorry, to clarify, I meant: HTTPS that works automatically. By starting the server, it's starting HTTPS by default. It gets or generates a certificate for you and renews it, etc.

In this case, not in the built-in Deno.serve case. Certificate management is definitely a challenge, especially for local development.

Reply on news.ycombinator.com