markhildreth / stunne Goto Github PK

Have it be able to respond to Binding requests to start.

Adhere to the "Server Behavior" section of RFC 5780 for the simple server. Specifically:

• Run the server such that it is bound to two addresses, and two ports. This should mean starting up four sockets. Error if any of the four sockets cannot be created.
  • Address A, Port A
  • Address A, Port B
  • Address B, Port A
  • Address B, Port B
• For each socket, handle binding requests such that the "OTHER-ADDRESS" attribute includes the opposite address/port (e.g., the socket for Address A, Port B should return address B, Port A).

It seems a bit overkill to use Bytes for encoding. Bytes makes more sense in a situation where data is being streamed (e.g., over TCP) with one thread pushing to the buffer while another reads. With the ability to read an entire datagram at once the only niceity is
the API, but with an unnecessary Arc overhead.

Additionally, I'm fine with an API that requires the user to specify the buffer size and error if the buffer would be overwhelmed. That's usually an indication that we should reject the data to begin with.

Implement "CHANGE-REQUEST" in the server, allowing a server to respond to a binding request from a different IP and/or port.