On Thu, 26 Feb 2015 16:59:05 +0100 Victor Stinner <[email protected]> wrote: > 2015-02-26 16:55 GMT+01:00 Antoine Pitrou <[email protected]>: > > That's not a use case, just some code :-) > > > > What is the protocol you are handling? > > It's not a known protocol. It's just data serialized by msgpack. The > code comes from the Ceilometer project of OpenStack. > > The server only receives data, it doesn't send UDP packets.
Are you implementing the server? I think a "stream"-like functionality would be mostly useful for clients. A server is better suited to the traditional Protocol idiom IMHO. In any case, in UDP you want the server to send a response to the client (if only a "ACK"); otherwise the client doesn't know whether the message was received or not. On the client side, a "client" object would make sense to expose sendto() and recvfrom(), I guess. You also want some timeout handling... Regards Antoine.
