Cloud Foundry and IOT protocol support
summary
Plans add non‑HTTP routing to Cloud Foundry by implementing a TCP route emitter + TCP router inside Diego/Lattice so apps can bind front‑end IP:port pairs (examples: MQTT on 1883, XMPP on 5222) and receive TCP traffic directly. Prototype routes a netcat app successfully. Limits: 64K ports per router instance and front‑end IP scarcity if clients demand standard ports; UDP is not supported yet. Changes require Cloud Controller updates, health checks and zero‑downtime handoffs.
AI-written summary · about
