3 ms·
RFC 3117 – On the Design of Application Protocols (2001)
- 0xbadcafebee 4y agoWow, what a blast from the past. Protocols that don't sit on top of HTTP.
- eternalban 4y agoDo you know the skinny on BEEP? That (via Rose) are what lead me to this rfc. Wondering if it panned out in practice.
- kjs3 4y agoAnd written by Marshall Rose. Elegant tools for a more civilized age.
- 10000truths 4y agoIn hindsight, the idea that ambiguous text-based parsing with in-line delimiters was considered a hallmark of a "simple protocol" is quite silly. Yes, such protocols are simple to implement for the happy path - it certainly made sense back when people primarily interacted with networks through the shell or a REPL. But it's clear that a sound and scalable wire format designed today should use binary encodings for compactness and performance, explicit lengths instead of delimiters for variable-length data to avoid the complexity of escape sequences, and fixed-length fields placed before variable-length fields to minimize memory allocation churn.
- billpg 4y agoNeeds more JSON.