jgd@csd4.csd.uwm.edu (John G Dobnick) (11/02/89)
From article <272@lib.tmc.edu>, by sob@lib.tmc.edu (Stan Barber): > NNTP 1.6 will be out in January. I hope that will be close to the last release > before we start to revise the RFC and add some functionality. > > Comments on anything about NNTP are always welcome. I don't know if this is a bug, an oversight, a protocol flaw, or what, but... The NNTP RFC states that a "." in column 1 will be doubled for transmission, so as not to be confused with the "eof" marker. The supplied (UNIX flavor) library does this automatically. However, the library routines do not *strip* this additional "." on reception. The net result is that if I "write" something to NNTP and then "read" it back, I get something different. I find this both non-orthogonal and annoying. Will this situation be addressed in the RFC revision? Or perhaps, if this is a "bug", in a future code revision? Thank you, -- John G Dobnick Computing Services Division @ University of Wisconsin - Milwaukee INTERNET: jgd@csd4.csd.uwm.edu UUCP: uunet!uwm!csd4.csd.uwm.edu!jgd "Knowing how things work is the basis for appreciation, and is thus a source of civilized delight." -- William Safire