poll: have you ever designed a protocol that uses TCP or UDP directly? (vs using protocols that are based on TCP/UDP like DNS, HTTP, SSH, etc)

(you can pick more than one)

yes, TCP
36.1%
yes, UDP
24.3%
no, but I’ve used protocols based on them
37%
other
2.6%
Poll ended at .
@b0rk what does "used HTTP to do handshaking because it has convenient headers, then used the request and response bodies as a bidirectional channel for a different protocol" count for? :')
@iximeow @b0rk have you considered using WebSocket? Was it too onerous? (Serious question because a few of the WS features are a PITA if I recall)

@unsaturated @b0rk i've remarked that what i ended up with is basically "websockets but bad", it's true!

in my case the data in headers is very different from data in bodies, to the point that if it were over TCP or WS i'd have probably have different connections for the two to make the data processing context very clear. otherwise either would be totally fine instead, yeah