Re: About word-encoding (RFC2047) design
- From: mem@xxxxxxxxxx (Mark E. Mallett)
- Date: Wed, 9 Aug 2006 17:57:58 +0000 (UTC)
In article <Pine.OSX.4.64.0608090957200.4967@xxxxxxxxxxxxxxxxx>,
Mark Crispin <mrc@xxxxxxxxxxxxxxxxxx> wrote:
If you want to see why we have such problems, just look at the thread with
subject "ESMTP AUTH PLAIN" in this newsgroup. A correct understanding of
how to do this requires thorough reading and understanding of three
different RFCs. Most people refuse to do this; instead, they guess by
empirical testing and they get it wrong.
Oh-oh, have I said something wrong?
Personally, I find necessary:
- a ton of reading of RFCs and documents;
- referring to same RFCs and documents continually forever after;
- often, reading of existing code;
- a bunch of empirical testing to test understanding of the readings;
- a bunch of interoperability testing to pit others' understandings
of the reading against one's own;
- passage of time to find out all the gotchas, one by one, if ever.
And then, once you think you are through all that, others to find problems
and show you just how wrong you can be :)
mm
.
- Follow-Ups:
- Re: About word-encoding (RFC2047) design
- From: Mark Crispin
- Re: About word-encoding (RFC2047) design
- References:
- About word-encoding (RFC2047) design
- From: stefano . sabatini-lala
- Re: About word-encoding (RFC2047) design
- From: Mark Crispin
- About word-encoding (RFC2047) design
- Prev by Date: Re: About word-encoding (RFC2047) design
- Next by Date: Re: About word-encoding (RFC2047) design
- Previous by thread: Re: About word-encoding (RFC2047) design
- Next by thread: Re: About word-encoding (RFC2047) design
- Index(es):
Relevant Pages
|