Out of scope rfcs/out-of-scope/rfc-bun-tcp.md

Bun.connect / Bun.listen — raw TCP

Moved backlog → out-of-scope. Raw TCP sits one rung below where a

Out-of-scope (2026-05-31)

Moved backlog → out-of-scope. Raw TCP sits one rung below where a meta-framework operates — it's a runtime/library concern. patties is HTTP-first by identity; the named trigger ("a non-HTTP transport story") would mean becoming a different product, not picking up a parked feature. Permanent no. Kept as a discovered-and-dismissed record (pairs with [[rfc-bun-udp]]).

Summary

Bun's TCP primitives. Lower-level than Bun.serve. Useful for hosting non-HTTP protocols.

Why backlog

Patties is an HTTP-first meta-framework. Raw TCP doesn't fit the current spec set. Adoption would require a new subsystem ("custom transports").

This entry is borderline out-of-scope: if we never host non-HTTP protocols, this RFC will move to rfcs/out-of-scope/.

Trigger to promote to draft

A clear non-HTTP use case lands (gRPC, raw socket game server, etc.) and we decide patties wants to own it.

Bun-unique classification

Bun-faster — node:net has the same surface; Bun's is faster. Capability isn't unique.

Open questions when promoted

  • Does patties even want to be in this business? (Current stance: no.)