You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to be able to mark the outgoing response packets with TOS values to support QOS based on different incoming client requests. Would it be reasonable to expose the Conn in http.ResponseWriter? Or perhaps enable some other way to support TOS?
The text was updated successfully, but these errors were encountered:
I'd rather not expose the conn. It leads to people being too clever and messing with the stream. CloseNotifier and Hijack are annoying enough to maintain.
I think this is a bizarre enough requirement (I've never head of anybody ever setting TOS based on the HTTP request) that it's not worth supporting directly. I think you can just write a net.Listener implementation that tracks the underlying TCP conn fds, returns a RemoteAddr() that net/http puts in stringified form in Request.RemoteAddr, then an http.Handler wrapper which unwraps that RemoteAddr string to find the TCP connection and resets RemoteAddr to its usual form.
It sounds kinda hacky, but so is the original problems, so it seems fitting.
I'd like to be able to mark the outgoing response packets with TOS values to support QOS based on different incoming client requests. Would it be reasonable to expose the Conn in http.ResponseWriter? Or perhaps enable some other way to support TOS?
The text was updated successfully, but these errors were encountered: