[Feat] Reverse Proxy bound to multiple ports

[Mushoz]

I saw you were interested in implementing this as a reverse proxy layer between a client and a LLM openai compatible backend, due to popular request on your Reddit post. Sessions would be managed through a user_id in each request. It would be awesome if this reverse proxy could bind to a port range instead of a single port, and each port would be tied to its own memory. This way, clients without the ability to add a user_id to each request could still work by selecting a unique port for each client instead of passing a user_id. That way, this reverse proxy could be implemented without requiring ANY client support whatsoever. Just point each client towards this proxy each using its own port and off you go. Thoughts?

[chattytak]

I'm not sure if it's appropriate to request a feature that hasn't been implemented yet, but if the goal is simply to run multiple instances for multiple users using multiple ports, wouldn't it suffice to run multiple instances of a single-port process within Docker containers or similar?
Isn't this just a wasteful idea for source code that stores multiple users' data in a single data store using user_id as the key?

[sll00]

I'll tack this on here, since reverse proxy is prerequisite, but when/if that feature becomes available - would anyone be interested in a little OpenCode plugin which sets user_id upon session creation?