Show HN: PocketBase – Open Source realtime backend in one file

Re:Show HN: PocketBase – Open Source realtime backend in one... by randomwebdev on Thursday July 07, 2022 @10:21AM (#32014466)

Yes, I'm aware of this limitation, but PocketBase uses HTTP2 when combined with the --https flag (this is by go's default net/http implementation) so it shouldn't be too much of a concern.

[ Parent | on HN ]

Re:Show HN: PocketBase – Open Source realtime backend in one... by antholeole on Thursday July 07, 2022 @10:26AM (#32014525)

First time I’ve heard about the 6 connection limit.

I’m not fully understanding the response - are you saying that the limit is not imposed if you use https? Or am I reading wrong?

[ Parent | on HN ]

Re:Show HN: PocketBase – Open Source realtime backend in one... by randomwebdev on Thursday July 07, 2022 @10:37AM (#32014675)

Go's default `net/http` package will serve HTTP2 when a https configuration is provided (also most web browsers don't support h2c, aka. HTTP2 without tls).

The default limit of ~100 connections should be more than enough for most applications (additionally, the JS SDK client maintains a single SSE connection for a page no matter to how many things the user has subscribed, so that also helps).

[ Parent | on HN ]

Re:Show HN: PocketBase – Open Source realtime backend in one... by futhey on Thursday July 07, 2022 @11:23AM (#32015261)

HTTP/1.1 has a limit, set by each individual browser vendor, for the maximum number of connections between a client and a unique server domain. So, if you exceed 6 simultaneous connections to that server (across multiple tabs and windows), it will move the request to a stalled state (like a queue) until one request is completed.

Best solution today is to move to http2 on your server -- which has an SSL (TLS 1.2) requirement.

Looks like pocketbase implements this. If you use another server, like nginx, you have to enable this for each site.

[ Parent | on HN ]