> usual unix on-disk representation... Not that this should stop someone
> from designing a kick butt mail system which uses CRLF on disk
> representations... after all if you're doing IMAP and POP why do you care
> if unix tools can read the files or not?
Besides, whoever invented the myth that crlf line endings are a problem
for unix tools?
> Yeah, now imagine the joy of the IMAP server with on-disk LF files... the
> IMAP protocol allows random-access to messages... try skipping ahead N
> bytes in the CRLF representation when you've only got the LF
> representation.
>
> And you thought HTTP was dumb :)
Incidentally, HTTP has the exact same problem. Just because much software
ignores the crlf requirement doesn't mean that it doesn't exist, you know.
*All* "real" Internet protocols use crlf line endings exclusively.
As for crlf on-disk in unix, well, I hear the big news transit servers,
for example, do it that way.
Personally, I'd even keep dot escapes on-disk.
MfG Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/