Alex / KATT

Closing this for now as I want us to focus on the `next`-branch

Could you show some mock code both front and back how you'd ideally want to use such a thing? Would help my thinking around it. As you know, trpc is...

FYI you can do this to circumvent the 4mb limit: ```ts import { createContext } from 'server/context'; import { appRouter } from 'server/routers/_app'; import * as trpcNext from '@trpc/server/adapters/next'; export...

Will be part of #1937 so closing this in favor of that one

Just as a note here, this probably should be a breaking change where we get rid of `.cancel()` and our own odd cancellable promise abstractions. > @IgnusG @KATT would you...

SSE should be possible to add alongside WebSockets. I prefer WS myself as I don't have to think about max concurrent connection limit and my application doesn't have user numbers...

Isn't scaling with SSE similar though, or am I missing something? It's still a persistent connection between a client and server(s) that also needs to be scaled.

Scaling is not my area of expertise, but with WS and the current setup it should scale seamlessly on things like k8s/render.com - we'll listen to a `SIGTERM` and broadcast...

I'll reopen this and see if someone wants to work on it for the next major :)

The way I deal with this is that I skip SSR on queries that depend on external services. Quite curious to implement a timeout thought if you think it would...