So testing things that work is easy. What I'm more concerned with,
right now, is the negative testing: testing the things that shouldn't
work. [Something that most programmers forget to do.]
So, I can trivially create /an NNTP server/ that replies with the wrong greeting line, or perhaps no line at all.
Reading RFC 3977, section 3.1, I can get the sense that
201This is a valid response line CR LF
It's easy to create these examples, and then have an NNTP library return
or throw an error (yes, even in C; we just use longjmp()), but how would
end user software want to deal with such cases?
How do people using newsreaders want to log such errors, and/or complain about it? To whom?
It's easy to create these examples, and then have an NNTP library return
or throw an error (yes, even in C; we just use longjmp()), but how would
end user software want to deal with such cases?
How do people using newsreaders want to log such errors, and/or complain about it? To whom?
What I'm wondering about, is how the software should behave if the first
line is simply invalid.
Reading RFC 3977, section 3.1, I can get the sense that
201This is a valid response line CR LF
but nobody does it in practice?
It's easy to create these examples, and then have an NNTP library return
or throw an error (yes, even in C; we just use longjmp()), but how would
end user software want to deal with such cases?
How do people using newsreaders want to log such errors, and/or complain about it? To whom?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 62:31:14 |
Calls: | 6,712 |
Files: | 12,244 |
Messages: | 5,355,896 |