|
+ Each command start with <STRING> <NUMBER> with possible leading/trailing
whitespace. <STRING> specifies the command name, <NUMBER> the size of
the command header, which uses a key-value format, kind of like ini.
Key-value parser is not yet implemented, but should be fairly simple to do.
+ The content of the message should be lark-encoded, essentially just that
each '=' in the text is replaced by '>=' (or something) so that the stream
of headers + message becomes self-synchronizing (kind of at least?)
|
