First of all, congratulations on open sourcing Pingora and thank you for continuing to work on it!
In the linked blog post, you mention that Pingora works with UDP.
Pingora provides libraries and APIs to build services on top of HTTP/1 and HTTP/2, TLS, or just TCP/UDP.
I read relevant sections of Pingora source code, and I believe you made a typo. I think instead of UDP (User Datagram Protocol) you meant UDS (Unix domain socket). For example, HttpPeer can be constructed with TCP or UDS. Another example: SocketAddr is an enum over Inet(StdSockAddr) and Unix(StdUnixSockAddr).
Describe the bug
First of all, congratulations on open sourcing Pingora and thank you for continuing to work on it!
In the linked blog post, you mention that Pingora works with UDP.
I read relevant sections of Pingora source code, and I believe you made a typo. I think instead of UDP (User Datagram Protocol) you meant UDS (Unix domain socket). For example,
HttpPeer
can be constructed with TCP or UDS. Another example:SocketAddr
is an enum overInet(StdSockAddr)
andUnix(StdUnixSockAddr)
.Pingora info
N/A
Steps to reproduce
Search source for
UDP
andUDS
.Expected results
Find references to
UDP
.Observed results
Only found references to
UDS
.Additional context
N/A