
31
Protocol design: textual
SMTP (RFC 822), HTTP, SIP, RTSP:
random textual: ftp, POP, IMAP, gopher, . . .➠ new parser for each
protocol
SMTP, HTTP, SIP, RTSP
–
: method, object, attribute: value;parameter, [body]
–
: status code, message, [body]
binary data not important
extensions: PEP, JEPI, PICS, ...
easy to parse & generate for Tcl, Perl, Python, . . .
overhead (space, time)? unidirectional?
but HTTP: not object retrieval, state (RTSP), . . .
Kommentare zu diesen Handbüchern